Prof. Roy Levow Session 10. Inputs the Client Checkpoint Questions to Be Answered During Client...

22
Prof. Roy Levow Session 10

Transcript of Prof. Roy Levow Session 10. Inputs the Client Checkpoint Questions to Be Answered During Client...

Page 1: Prof. Roy Levow Session 10.  Inputs the Client Checkpoint  Questions to Be Answered During Client Checkpoint  Adjusting Functionality for the Next.

Prof. Roy Levow

Session 10

Page 2: Prof. Roy Levow Session 10.  Inputs the Client Checkpoint  Questions to Be Answered During Client Checkpoint  Adjusting Functionality for the Next.

Inputs the Client Checkpoint Questions to Be Answered During Client

Checkpoint Adjusting Functionality for the Next Cycle

Plan

Page 3: Prof. Roy Levow Session 10.  Inputs the Client Checkpoint  Questions to Be Answered During Client Checkpoint  Adjusting Functionality for the Next.

Explain the significance of each input to the client checkpoint

Assess the status of the completed cycle relative to its plan

Describe the inputs to the next cycle plan Explain the outputs of the client

checkpoint

Copyright 2007 John Wiley & Sons, Inc. Chapter 17 3

Page 4: Prof. Roy Levow Session 10.  Inputs the Client Checkpoint  Questions to Be Answered During Client Checkpoint  Adjusting Functionality for the Next.

Planned versus Actual Functionality Added Why wasn’t the planned functionality added in

this cycle? Explain how the functionality will be added in

future cycles Scope Bank

Let customer decide what proposed changes will be added in future cycles

Copyright 2007 John Wiley & Sons, Inc. Chapter 16 4

Page 5: Prof. Roy Levow Session 10.  Inputs the Client Checkpoint  Questions to Be Answered During Client Checkpoint  Adjusting Functionality for the Next.

What was planned? What was done? Is the version scope still valid? Is the team working as expected? What was learned?

Copyright 2007 John Wiley & Sons, Inc. Chapter 17 5

Page 6: Prof. Roy Levow Session 10.  Inputs the Client Checkpoint  Questions to Be Answered During Client Checkpoint  Adjusting Functionality for the Next.

Inputs Any functionality completed during the previous cycle Any functionality planned but not completed in the

previous cycle The functionality planned for this cycle The functionality planned for all the cycles beyond the

next one All learning and discovery that took place in all previous

cycles (Scope Bank) Any items still remaining on the Issues Log Any changes that took place in the business

environment during the previous cycles

Copyright 2007 John Wiley & Sons, Inc. Chapter 17 6

Page 7: Prof. Roy Levow Session 10.  Inputs the Client Checkpoint  Questions to Be Answered During Client Checkpoint  Adjusting Functionality for the Next.

Outputs Updated functionality list Reprioritized functionality list Next cycle length

Copyright 2007 John Wiley & Sons, Inc. Chapter 17 7

Page 8: Prof. Roy Levow Session 10.  Inputs the Client Checkpoint  Questions to Be Answered During Client Checkpoint  Adjusting Functionality for the Next.

Checking Explicit Business Outcomes Reviewing Lessons Learned for Next

Version Functionality Assessing APF for Improvements

Page 9: Prof. Roy Levow Session 10.  Inputs the Client Checkpoint  Questions to Be Answered During Client Checkpoint  Adjusting Functionality for the Next.

Explain the significance of the Post-Version Review

Describe the deliverables from a Post-Version Review

Conduct a Post-Version Review Extract lessons learned from the version

project

Copyright 2007 John Wiley & Sons, Inc. Chapter 18 9

Page 10: Prof. Roy Levow Session 10.  Inputs the Client Checkpoint  Questions to Be Answered During Client Checkpoint  Adjusting Functionality for the Next.

To Improve Product To Improve Process To Determine if Business Value is Being

Delivered

Copyright 2007 John Wiley & Sons, Inc. Chapter 18 10

Page 11: Prof. Roy Levow Session 10.  Inputs the Client Checkpoint  Questions to Be Answered During Client Checkpoint  Adjusting Functionality for the Next.

Check Explicit Business Outcomes The success of the APF project is the business

value it delivered Review Lessons Learned for Next Version

Functionality Assess APF for Improvements

Copyright 2007 John Wiley & Sons, Inc. Chapter 18 11

Page 12: Prof. Roy Levow Session 10.  Inputs the Client Checkpoint  Questions to Be Answered During Client Checkpoint  Adjusting Functionality for the Next.

Proof-of-Concept Cycle Revising the Version Plan Embedding the APF in Other Approaches Extreme Project Management Comparing Project Approaches

Page 13: Prof. Roy Levow Session 10.  Inputs the Client Checkpoint  Questions to Be Answered During Client Checkpoint  Adjusting Functionality for the Next.

Embed the APF in other approaches Use the APF for proof of concept Adapt the APF to revise the version plan Identify an extreme project Describe the four phases of the Extreme

Project Management approach Understand how Extreme Project

Management clarifies the goal and converges to a solution

Copyright 2007 John Wiley & Sons, Inc. Chapter 19 13

Page 14: Prof. Roy Levow Session 10.  Inputs the Client Checkpoint  Questions to Be Answered During Client Checkpoint  Adjusting Functionality for the Next.

Proof-of-Concept Cycle Used to help make business case for project First cycle of APF project Steps

The creation of a prototype A feasibility study The writing of use cases Storyboarding Any other activity to demonstrate business plan

Revising Version Plan The first few cycles generates numerous change ideas

and issues Client may decide to change version plan

Copyright 2007 John Wiley & Sons, Inc. Chapter 19 14

Page 15: Prof. Roy Levow Session 10.  Inputs the Client Checkpoint  Questions to Be Answered During Client Checkpoint  Adjusting Functionality for the Next.

In TPM In the WBS, leave a functionality undefined Place undefined functionality in Network

Diagram Use APF for the undefined functionality

Copyright 2007 John Wiley & Sons, Inc. Chapter 19 15

Page 16: Prof. Roy Levow Session 10.  Inputs the Client Checkpoint  Questions to Be Answered During Client Checkpoint  Adjusting Functionality for the Next.

High Speed – Project is innovative, groundbreaking, and vital to organization. Speed is essential

High Change – Uncertainty about goal and solution necessitates constant change

High Uncertainty – Time and cost are unknown

Copyright 2007 John Wiley & Sons, Inc. Chapter 19 16

Page 17: Prof. Roy Levow Session 10.  Inputs the Client Checkpoint  Questions to Be Answered During Client Checkpoint  Adjusting Functionality for the Next.

Iterative After each cycle, decision

made to continue or cancel Scope is unknown Client most involved (makes

decision to go on) No constrained scope triangle

Copyright 2007 John Wiley & Sons, Inc. Chapter 19 17

Page 18: Prof. Roy Levow Session 10.  Inputs the Client Checkpoint  Questions to Be Answered During Client Checkpoint  Adjusting Functionality for the Next.

Define the Project Goal xPM Project Overview Statement Establish a Project Timebox and Cost Establish Number of Cycles and Cycle

Length Trade-Offs in the Scope Triangle

Copyright 2007 John Wiley & Sons, Inc. Chapter 19 18

Page 19: Prof. Roy Levow Session 10.  Inputs the Client Checkpoint  Questions to Be Answered During Client Checkpoint  Adjusting Functionality for the Next.

Defining How the Project Will Be Done Conditions of Satisfaction Scenarios, Stories, and Use Cases Prioritizing Requirements Identifying the First Cycle Deliverables Go / No-Go Decision Planning for Later Cycles

Copyright 2007 John Wiley & Sons, Inc. Chapter 19 19

Page 20: Prof. Roy Levow Session 10.  Inputs the Client Checkpoint  Questions to Be Answered During Client Checkpoint  Adjusting Functionality for the Next.

How this Phase Differs Time for exploration and discovery Subteams share ideas and information

Assign Resources Establish Cycle Plan Collaboratively Produce Deliverables

Copyright 2007 John Wiley & Sons, Inc. Chapter 19 20

Page 21: Prof. Roy Levow Session 10.  Inputs the Client Checkpoint  Questions to Be Answered During Client Checkpoint  Adjusting Functionality for the Next.

Apply Learning and Discovery from the Previous Cycle

Revise the Project Goal Reprioritize Requirements Make the Go / No-Go Decision for the

Next Cycle

Copyright 2007 John Wiley & Sons, Inc. Chapter 19 21

Page 22: Prof. Roy Levow Session 10.  Inputs the Client Checkpoint  Questions to Be Answered During Client Checkpoint  Adjusting Functionality for the Next.

Copyright 2007 John Wiley & Sons, Inc. Chapter 19 22