Managing Scope, Time, Cost and Team in Agile

Madhu Expedith PMP®, CSM, CSQA, ISTQB-CTFL, ITIL v3.0

Principal Consultant, Infosys Limited

Agenda

Part 1:

• Responding to change over following a plan

• Overview of Scrum Framework

Part 2:

• Revisit PMBOK Process Groups and Knowledge Areas

• Managing Scope, Time, Cost and Team in Scrum and

alignment with PMBOK

• Q&A Session

Slide 2

Responding to change over following a plan

Slide 3

For Discussion:

Can project teams respond to changes in the most efficient manner within

budgeted cost and desired quality?

Scrum Framework

Slide 4

Overview of Scrum Framework – 3-4-3

3 Roles

• Product Owner

• ScrumMaster

• Scrum Development Team

4 Ceremonies

• Sprint Planning Meeting

• Daily Scrum / Standup

• Sprint Review Meeting

• Sprint Retrospective

Slide 5

3 Artifacts

• Product Backlog

• Release Backlog

• Sprint Backlog

• Sprint Burndown Product Backlog

High Priority

Low Priority

For Discussion:

What are the responsibilities of a traditional

Project Manager?

Overview of Scrum Framework – Sprint Planning

Slide 6

• What is a Product Backlog?

• What are User Stories?

As a < role > I want to < action / function > so that I can

<justification / objective>. This story is done when…

< List acceptance criteria >

• Sprint Planning

• 3 Cs: Card, Conversation and Confirmation

• Story Point Estimation

• Sprint Backlog Items broken down into Sprint Tasks

• Team Commitment

• The importance of having a conversation

For Discussion:

Interpret the following statement:

“Mary had a little lamb”

Overview of Scrum Framework – Daily Scrum

Slide 7

• Daily Standup

• 15 mins

• Not a Status Meeting

• Team Synchronization

• Best Practice

• What did I do yesterday?

• What am I planning to do today?

• What are my impediments?

• Task Board

Overview of Scrum Framework – Sprint Review

Slide 8

• Sprint review

• Demonstrate working

product

• Show and tell

• Mini UAT at the end of

each sprint

• Accept items that are

“done”

• Return incomplete

items to the Product

Backlog

• Velocity

• Running average of

accepted story points

• Fixed Team

• Fixed Sprint Duration

Overview of Scrum Framework – Sprint Retrospective

Slide 9

Sprint

Retrospective

• Team

Reflection

• Process

Reflection

• What worked

well

• What did not

work well

• Not a post-

mortem

Scope, Time, Cost and Team (Human Resource)

Scope Time

Cost Team

Scope Time

Cost Team

Waterfall Agile

What is fixed?

PMBOK Process Groups and Knowledge Areas

Process Groups Knowledge Areas

Initiating Planning Executing Monitoring & Control

Closing

Project Integration Management

Project Scope Management

Project Time Management

Project Cost Management

Project Quality Management

Project Human Resource Management

Project Communications Management

Project Risk Management

Project Procurement Management

Managing Scope

• Requirements: User Stories

/ Product Backlog Items in

the Product Backlog

• Iterative planning (scope for

the sprint)

• Fixed team that is self-

organizing and cross-

functional

• Scope frozen within the

sprint

• No Change Requests!

Slide 12

Managing Time

• Time is fixed – all activities

are time-boxed

• Sprint Planning

• Sprint Backlog Items

broken down into Sprint

Tasks

• Team capacity based

planning

• Release Planning and

Scheduling

Slide 13

Managing Cost

• Estimate Cost

• Determine Budget

• Value-driven development

Slide 14

Managing Team

• Fixed team

• Co-location preferred

• Self-organizing

• Cross-functional

Slide 15

The Agile Manifesto and the Principles behind Agile Manifesto

Agile Manifesto

1. Individuals and interactions over processes and tools

2. Working software over comprehensive documentation

3. Customer collaboration over contract negotiation

4. Responding to change over following a plan

That is, while there is value in the items on the right, we value the items on the left more.

Slide 16

Principles behind Agile Manifesto

1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.

2. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.

3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.

4. Business people and developers must work together daily throughout the project

5. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.

6. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.

7. Working software is the primary measure of progress.

8. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.

9. Continuous attention to technical excellence and good design enhances agility.

10. Simplicity--the art of maximizing the amount of work not done--is essential.

11. The best architectures, requirements, and designs emerge from self-organizing teams.

12. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

References

Slide 17

• http://agilemanifesto.org/

• http://agilemanifesto.org/principles.html

• http://www.scrumalliance.org/pages/scrum_101

• http://www.mountaingoatsoftware.com/scrum/overview

• http://www.scrumalliance.org/articles/39-glossary-of-scrum-terms#1110

• http://www.scrumalliance.org/articles/386-a-sprint-is-not-a-mini-waterfall

• http://www.scrumalliance.org/articles/392-agile-testing-key-points-for-

unlearning

Done!

Thank you…

Slide 18

The agility lies in the Agile practices, rather than in the

overarching framework itself…