developing an agile schedule in microsoft project - it is possible!

© International Institute for Learning, Inc., All rights reserved. 1Intelligence, Integrity and Innovation © International Institute for Learning, Inc., All rights reserved.

Thank you for joining us today. This webinar is brought to you by IIL – a global

leader in:Project, Program and Portfolio Management

Microsoft® Project and Project ServerLean Six Sigma | Business Analysis

Agile | PRINCE2® | ITIL®

Leadership and Interpersonal Skills

Developing an Agile Schedule in Microsoft®

Project – It is Possible!

© International Institute for Learning, Inc., All rights reserved. 2Intelligence, Integrity and Innovation

Global IIL CompaniesIIL USIIL Asia (Singapore)

IIL AustraliaIIL BrasilIIL CanadaIIL ChinaIIL Europe (United Kingdom)

IIL FinlandIIL France

IIL GermanyIIL Hong KongIIL HungaryIIL IndiaIIL JapanIIL Korea (Seoul)

IIL MéxicoIIL Middle East (Dubai)

IIL Spain


What is a Project?


A temporary endeavor undertaken to create a unique product, service, or result

What is a Project?

G – Goal Oriented U – UniqueF – FiniteI – Interdependent Activities


Project Management Knowledge Areas and Constraints


Waterfall


Key characteristics of the Waterfall (classic) method:

A development method that is:LinearSequential

It has distinct goals for each phase of development.Once a phase is completed, there is no turning back.

Waterfall – Key Characteristics


Key stages / phases of development:

Waterfall – Diagrammatic Representation

Requirements

Design

Implementation

Verification

Maintenance


Waterfall Projects – The V DiagramKey stages / phases of development:

ConceptRequirements

SystemRequirements

High levelDesign

DetailDesign

SystemDevelopment

UnitTest

Sub-SystemVerification

SystemVerification

SystemValidation

UnitTest Plan

Sub-SystemVerification

Plan

System Verification Plan

System Validation Plan

Strategicneed

Benefitsrecovery


Waterfall Project ManagementDiagrammatic view of the Waterfall approach to parameters:

Features

Quality?

Time Cost

Fixed

Variable

Plan driven

Derives and delivers to a specificationProduces a plan from the specificationThe plan indicates likely time and cost

Change is a distraction


Delivers everything neededRegulatory compliance projectsGovernance proceduresDocumentationKnown / repeatable processUnified planningSignificance of Project ManagerDelegation to and by Project Manager

The Strengths of WaterfallStrengths of Waterfall / PMIBoK


Demo


What do we mean by “Agile”?


Key characteristics of the Agile method:A development method that is:

IterativeIncrementalEmbraces change

Delivers deployable product early for ROIDelivers a Minimum UsableSub-seT (MUST) to time

Agile – Key Characteristics


Agile – Diagrammatic RepresentationKey aspects of development:

Requirements

Design

Implementation

Verification

Maintenance

Iterative – from

anywhere to anywhere


Agile Project ManagementDiagrammatic view of the Agile approach to parameters:

Fixed

Variable

Value driven

Understands and delivers to a business valueProduces to agreed and fixed time (and cost)Does not compromise quality

Change is embracedFeatures

Quality

Time Cost


Strengths agile:Delivers minimum usable subsetDelivers on time and to costIterative development for evolving solution Economical on documentationHigh degree of empowermentFlexible processesCollaboration of whole team

The Strengths of Agile


Plan vs. Value Driven

Source: Ryan Matena, “Ready for Agile,” [email protected], 9/28/06


Plan-Driven MethodsAll requirements are detailed and approved before development.Changes are approved through a formal change control process.Emphasis is placed on documents as deliverables.Stakeholders see the product at the end of the lifecycle.

Agile MethodsRequirements are detailed just before they are developed.Requirements changes are integrated into plans.Emphasis is placed on working software over documentation.Stakeholders see the evolving product at the end of every iteration.

Contrasting Plan-Driven and Agile Methods


Plan-Driven MethodsDetailed plans are created at the start of the project.Plans are typically activity-based, and not based on feature priority.Testing and integration are performed at the end of the lifecycle.

Agile MethodsPlans are built iteratively to incorporate new knowledge and changes.Plans are feature-based.Features are developed based on priority.Testing and integration are performed in every iteration.

Contrasting Plan-Driven and Agile Methods


The Scrum Process

Product Backlog

Product Backlog

Sprint Planning Meeting

Sprint1-4 weeks

Daily ScrumEvery 24 hours

Potentially

Releasable Product Incremen

tSprint Review

Meeting


Release planning involves selecting features from the Product Backlog based on priority or the selected themes for a release.

Themes are groups of features that provide discrete sets of user or customer-valued functionality.

The release plan answers the question “When will you be done (or partially done)?”The release is accomplished through a series of iterations.

Release Planning


The Product Backlog is a list of features prioritized by business value.Detailed requirements in the backlog are often written as user stories.

User story format: As a <user role>, I want to <achieve some goal> so that I can <receive some benefit>.

The Product Backlog


Example User Story

As a book author, I want to be able to add search keywords and categories to my book details so that customers can easily find my book on the site.


Demo


Steps in release planning:1. Estimate and prioritize user

stories and themes.2. Select an iteration length.3. Estimate the number of user

stories the team can complete in an iteration (aka velocity).

4. Select a release date.

Planning a Release


Since cost is factored into the prioritization and planning processes, the team must estimate the effort involved in completing each user story.Two user story estimation techniques:1. Story points, which are a measure of relative size2. Ideal days, which is the amount of time a story takes to

develop with no interruptions

Estimating Story Cost


Story points are relative values based on the size or difficulty of a user story relative to other stories.

Can be numbers – e.g., 1, 2, 5, 8Or other size measures, such as t-shirt sizes – e.g., XXS, XS, S, M, L, XL, XXL

When you estimate using story points, you estimate the “bigness” of a user story compared to other stories.

Story Points


Velocity is a measure of the team’s rate of progress calculated by summing the size of the user stories that the team can complete during an iteration.

The team’s velocity = the number of story points (or ideal days) completed during an iterationVelocity can be based on observed velocity or a forecast based on the team’s capacity

Velocity


Velocity x Number of iterations in a release = the number of story points that can be completed in the releaseExample:

For the next release, two themes have been selectedThe total story point estimates for the themes = 80The team’s velocity is forecast at 10 story points per 2-week iterationThe release will be complete in 8, 2-week iterations, or 3 months

If the release date is already set, velocity can be used to determine the number of stories that can be completed in the release.

Velocity and Release Planning


A user can…

A user can…

A user can…

A user can…

A user can…

A user can…

A user can…

A user can…

A user can…

A user can…

A user can…

A user can…

A user can…

Example Release PlanIteration

#1Iteration

#2Iterations #3-5

A user can…6

A user can…4

2

2

4

3

3

6

6

4

3

6

4

3

4


During the iteration planning meeting, user stories are selected for an iteration based on the release plan, business value, and the size of the stories.

Each story is discussed and decomposed into the tasks that need to be done to complete it.

Tasks are estimated using ideal days or hours.Task estimates are done collaboratively with the whole team.

Iteration Planning


TASKS:Create entries in the UI for search keywordsCreate entries in the UI for search categoriesIntegrate keywords and categories into site search capabilitiesWrite unit testsExecute unit tests…

Example: User Stories to Tasks

As a book author, I want to be able to add search keywords and categories to my book details so that customers can easily find my book on the site.

USER STORY:


The iteration plan contains:The iteration goal and target velocityThe user stories selected for the iterationThe tasks needed to build the storiesThe estimates for the tasks in ideal days or hours

The Iteration Plan


Code the…4 ME

Code the…4 ME

Test the…4

Code the…6

Code the…4

Code the…4

Test the…4

Code the…2

Test the…1

Code the…2

Test the…1

Code the…6

Test the…3

A user can…

Example Iteration Plan (aka Team Board)

6

Code the…4

Test the…4 ME

YU

TY

User Stories Tasks In Progress Done

A user can…

6

Test the…4 ME

Code the…4 YU

Code the…4 TY

Test the…4 TY


Stories, Tasks, and Assignments

Code the…4 ME

Code the…4 ME

Test the…4

Code the…6

Code the…4

Code the…2

Test the…1

Code the…6

Test the…3

A user can…

6

Code the…4

Test the…4 ME

YU

TY

User Stories Tasks In Progress Done

Test the…4 ME

Story estimated in story points

Tasks estimated in

ideal days/hours

Tasks selected

by a team member to

work on


Demo


A burndown chart is a simple way to track progress during an iteration.To create a burndown chart, sum the task hours remaining once a day and plot it.

Using Burndown Charts to Track Progress


Example Burndown Chart

Task

Hou

rs

Days in Iteration

180160

100

120

140

80604020


Demo


We invite you to get a closer look at what IIL can do for you and your organization, by visiting www.iil.com or email [email protected] and let us know how we can meet your learning needs.Please connect with IIL Socially:

Like us on: facebook.com/IIL.incFollow us: twitter.com/IILGLOBALJoin our Discussions on LinkedIn

At IIL, Our Greatest Accomplishments are Yours

http://www.iil.com/

mailto:[email protected]

developing an agile schedule in microsoft project - it is possible!

Software