project management foundations series course 104 - agile project management concepts

50
Project Management Foundations Course 104 – Introduction to Agile Project Management Concepts

Upload: think-for-a-change

Post on 28-Jan-2015

117 views

Category:

Technology


0 download

DESCRIPTION

 

TRANSCRIPT

Page 1: Project Management Foundations Series Course 104 - Agile Project Management Concepts

Project Management Foundations

Course 104 – Introduction to Agile Project Management Concepts

Page 2: Project Management Foundations Series Course 104 - Agile Project Management Concepts

Target Student Audience

• Little to no experience with:– Formal Project Management Concepts

– PMI Project Management Body of Knowledge

– Agile Project Management Concepts

– SCRUM Methodology

• Frustrated with:– Poorly Organized Work Efforts

– Lack of Leadership in Project Efforts

– Applying “Waterfall-based” techniques to all projects

– Project management approaches that have excessive process and document requirements

Page 3: Project Management Foundations Series Course 104 - Agile Project Management Concepts

Course 104 – Introduction to Agile Project Management Concepts

Introduction to Agile Project Management Concepts

A Closer Look at SCRUM

Applying Agile PM to Your Organization

Demonstrate What You’ve Learned!

Segment One

Segment Two

QUIZ

Segment Three

Course Syllabus:

Page 4: Project Management Foundations Series Course 104 - Agile Project Management Concepts

Introduction to Agile Project Management Concepts

Page 5: Project Management Foundations Series Course 104 - Agile Project Management Concepts

What is Agile Project Management?

• Definition:– “Iterative method of determining requirements for engineering and

information technology development projects in a highly flexible and interactive manner”1

• Agile is most effective on projects that are:– Very complex for the end user or project sponsorship to technically

understand

– Difficult to fully define the full scope or set of requirements at the beginning of the project

– Likely to have many changes or updates during the project lifecycle

http://en.wikipedia.org/wiki/Agile_management

Page 6: Project Management Foundations Series Course 104 - Agile Project Management Concepts

1950s & 1960s

• Plan-Do-Check-Act (PDCA) Cycles

• Total Quality Management (TQM)

• Toyota Production System (TPS)

1970s & 1980s

• Lean Manufacturing

• Six Sigma

• Theory of Constraints (ToC)

1990s• Crystal Methods• Lean Software Development• Rational Unified Process (RUP)• Dynamic Software Development Method (DSDM)• Observe-Orient-Decide-Act Loop (OODA)• Feature Driven Development• eXtreme Programming (XP)• Adaptive Software Development• SCRUM Methodology

2000s:

• Software Development Life Cycle (SDLC)

• The Agile Manifesto • http://www.agilemanifesto.org

Historical Influences and Chronology of Agile Methodology

Page 7: Project Management Foundations Series Course 104 - Agile Project Management Concepts

The Agile Manifesto’s Statement of Values

Process and ToolsProcess and ToolsIndividuals and InteractionsIndividuals and Interactions over

Following a PlanFollowing a PlanResponding to ChangeResponding to Change over

Source: www.agilemanifesto.org

Comprehensive DocumentationComprehensive DocumentationWorking SystemsWorking Systems over

Contract NegotiationContract NegotiationCustomer CollaborationCustomer Collaboration over

While agile practitioners value the items on the left, they value the items on the right even more!

Page 8: Project Management Foundations Series Course 104 - Agile Project Management Concepts

The Twelve Principles of the Agile Manifesto

1. Customer satisfaction by rapid delivery of useful software

2. Welcome changing requirements, even late in development

3. Working software is delivered frequently (weeks rather than months)

4. Working software is the principal measure of progress

5. Sustainable development, able to maintain a constant pace

6. Close, daily cooperation between business people and developers

7. Face-to-face conversation is the best form of communication (co-location)

8. Projects are built around motivated individuals, who should be trusted

9. Continuous attention to technical excellence and good design

10. Simplicity is essential

11. Self-organizing teams

12. Regular adaptation to changing circumstances

Page 9: Project Management Foundations Series Course 104 - Agile Project Management Concepts

Key Agile Principles:• Focus on Customer Value – Align project,

product and team visions to deliver better product quality – faster and cheaper.

• Small Batches - Create a flow of value to customers by “chunking” feature delivery into small increments.

• Small, Integrated Teams - Intense collaboration via face-to-face communication, collocation, etc; diversified roles on integrated, self-organizing, self-disciplined teams.

• Small, Continuous Improvements – Teams reflect, learn and adapt to change; work informs the plan.

Delivering Customer Value with Agile Project Management

The right product, at the right time, for the right price.

•Higher Quality: “Designed-to-fit” product with flexibility to change.

•Increased Throughput: Iterative and incremental project and product “chunks” with earlier value delivery.

•Reduced Waste: Lean, efficient processes with lower costs and higher productivity.

Delivering Customer Value with Agile Project Management

The right product, at the right time, for the right price.

•Higher Quality: “Designed-to-fit” product with flexibility to change.

•Increased Throughput: Iterative and incremental project and product “chunks” with earlier value delivery.

•Reduced Waste: Lean, efficient processes with lower costs and higher productivity.

Agile Principles in Action

Page 10: Project Management Foundations Series Course 104 - Agile Project Management Concepts

Key Agile Practices:• Release Planning• Sprint Planning• Daily Scrum/Standup• Fixed-length sprints• Sprint Review• Sprint Retrospective

Identify top-priority items and deliver Identify top-priority items and deliver them rapidly using: them rapidly using:

• Small batchesSmall batches• Small integrated teamsSmall integrated teams• Small, continuous improvementsSmall, continuous improvements

Identify top-priority items and deliver Identify top-priority items and deliver them rapidly using: them rapidly using:

• Small batchesSmall batches• Small integrated teamsSmall integrated teams• Small, continuous improvementsSmall, continuous improvements

How The Agile Lifecycle Works

Page 11: Project Management Foundations Series Course 104 - Agile Project Management Concepts

Agile Software Development Methodology

Page 12: Project Management Foundations Series Course 104 - Agile Project Management Concepts

A Closer Look At SCRUM

Page 13: Project Management Foundations Series Course 104 - Agile Project Management Concepts

What is SCRUM?

• Definition:– “SCRUM is an iterative and incremental development framework for

managing technology projects and product development. Its focus is on a flexible, holistic product development strategy where a development team works as a unit to reach a common goal as opposed to a traditional, sequential (waterfall) approach.”

Page 14: Project Management Foundations Series Course 104 - Agile Project Management Concepts

How Scrum Works

• Projects are made up of self-organizing teams

• Requirements are captured as a list of tasks placed on a “product backlog” chart

– These task items make up what is known as a “user story”

• Product development is conducted along a series of month-long “sprints” made up of a logical amount of tasks that can delivered in that timeframe

• No specific design and development practices are prescribed

– The self-organizing teams determine the best way to successfully complete the tasks within the sprint

Page 15: Project Management Foundations Series Course 104 - Agile Project Management Concepts

What is a Sprint?

• Scrum projects make progress in a series of “sprints”

• Typical duration of each sprint is 30 days although anywhere between 2-6 weeks is usually acceptable

• The product outcome planned for the sprint is completely designed, built and tested during the sprint

• Once a sprint is started, it is allowed to finish without modification

©The Code Project Open License (CPOL)

Page 16: Project Management Foundations Series Course 104 - Agile Project Management Concepts

Scrum & Change Management

Before/After Sprint During Sprint

Page 17: Project Management Foundations Series Course 104 - Agile Project Management Concepts

Scrum Roles

• Product Owner

• ScrumMaster

• Scrum Team

Page 18: Project Management Foundations Series Course 104 - Agile Project Management Concepts

The Product Owner

• Represents the “Voice of the Customer”

• States requirements of the product as a “User Story”

• Defines the features of the product

• Decides on release date and content

• Is accountable for ensuring the product has a business need and value

• Prioritizes features according to the defined business need/value

• Adjusts features and priority every iteration (between sprints) 

• Accepts or rejects the work results both at the end of each sprint and at the final product review

Page 19: Project Management Foundations Series Course 104 - Agile Project Management Concepts

The ScrumMaster

• Represents management to the project

• Responsible for enacting Scrum values and practices

• Removes impediments

• Ensure that the team is fully functional and productive

• Enable close cooperation across all roles and functions

• Shield the team from external interferences

Page 20: Project Management Foundations Series Course 104 - Agile Project Management Concepts

The Scrum Team

• Typically limited to 5-9 people• “If the team can't be fed by two pizzas, then it's too

big” – Steve Bezos, CEO of Amazon

• Cross-functional skill sets

• Members should be dedicated full-time

• May be some exceptions for niche players

• Teams are self-organizing

• Membership should change only between sprints

Page 21: Project Management Foundations Series Course 104 - Agile Project Management Concepts

Scrum Activities

• Establish the Product Backlog

• Create the Sprint Backlog

• Sprint Planning

• Sprint Execution / Daily SCRUM

• Sprint Closing Activities

• Product Backlog Refining

Page 22: Project Management Foundations Series Course 104 - Agile Project Management Concepts

Establish The Product Backlog

• Completed and prioritized by the Product Owner

• A list of all desired work on the project

• A list of the “must have’s” vs. the “nice to haves’”

• Usually captured as a “user story” that describes the need, value and use of the item

• Reprioritized at the start of each sprint

Page 23: Project Management Foundations Series Course 104 - Agile Project Management Concepts

A Sample Product Backlog

User Story Initial EstimateAs a salesperson, I would like to allow a prospect to email me directly with questions

6

As a customer, I want to be able to order direct from the web 5

As a customer, I want to be able to cancel or change my order from the web

3

As a warehouse manager, I want to be able to get an automated “pick list” of the customer’s order emailed to my team

8

Eliminate paper handling between sales and the warehouse 8

Integrate with financial management systems 30

Integrate with inventory management systems 50

Page 24: Project Management Foundations Series Course 104 - Agile Project Management Concepts

Establishing the Sprint Backlog

• The Scrum Team selects items from the product backlog they can commit to completing within the planned sprint duration

• Sprint backlog is created based on the user stories selected

• Tasks are identified and each is estimated for time required

– 1 hour minimum to 40 hours maximum

• The ScrumMaster facilitates the discussion but the SCRUM Team is responsible for completion

• High-level design framework is considered to ensure the end product

As a salesperson, I would like to allow a prospect to email me directly with questions • Design mailto: form and interface (2)

• Position interface on ‘Contact Us’ Page (1)• Configure mail routing protocols (2)• Map mail routing and store in sprint design log

(1)

Page 25: Project Management Foundations Series Course 104 - Agile Project Management Concepts

Managing The Sprint Backlog

• Individuals sign up for work tasks of their own choosing

Work is never assigned

• Estimated work remaining is updated daily

• Any work that can’t be readily defined should be saved for the end of the sprint and updated as more becomes known

• Once the Sprint Backlog is defined, it is LOCKED and no changes can be made by those outside of the Scrum Team until the sprint is over

Any team member can add, delete or change the sprint backlog

Page 26: Project Management Foundations Series Course 104 - Agile Project Management Concepts

A Sample Sprint Backlog

TasksTasks

Design mailto: form and interface

Position interface on ‘Contact Us’ Page

Configure mail routing protocols

Map mail routing and store in sprint design log

MonMon

2

1

2

1

TuesTues

1

1

1

WedWed ThurThur FriFri

1

11 1

TOTAL EFFORT REMAINING 24 1 06

Page 27: Project Management Foundations Series Course 104 - Agile Project Management Concepts

Sprint Execution

The Daily Scrum:•Stand-up Meeting•No longer than 20 minutes•Anyone is welcome, but only Team Members, ScrumMaster, and Product Owner can talk•Daily Scrum is NOT a problem solving meeting•Three questions are asked of each Team Member:

1. What did you do yesterday?• Not a status report but a list of tasks

completed and started2. What are you working on today?

• A commitment to the Team about what you plan to accomplish

3. What is getting in your way?

The ScrumMaster will provide general status updates, discuss issue

resolution plans and conduct Q&A in a separate meeting following the

Daily Scrum

Page 28: Project Management Foundations Series Course 104 - Agile Project Management Concepts

Not StartedNot Started In ProgressIn Progress Verify / TestVerify / Test DoneDone

SCRUM Board

Map Mail Routing and Store In Sprint Design Log

Position Interface on ‘Contact Us’ Page

Design mailto: Form and Interface

Meet with Product Owner regarding question on different email addresses

Configure Mail Routing Protocols

Check Infrastructure

Test Mail Routing

Validated on 03/31

Page 29: Project Management Foundations Series Course 104 - Agile Project Management Concepts

“Real-World” SCRUM Board Example

Thanks to our friends at the Visual Management Blog! http://www.xqa.com.ar/visualmanagement/

Page 30: Project Management Foundations Series Course 104 - Agile Project Management Concepts

Sprint 1 Backlog

Sprint implementation days 5 Effort Remaining on implementation day…Trend calculated based on last 5 Days Totals 4 4 4 2 1Task name Story ID Responsible Status Est. 1 2 3 4 5Design mailto: form and interface 1 1 1Position interface on ‘Contact Us’ Page 1 1 1 1Configure mail routing protocols 1 1 1Map mail routing and store in sprint design log 1 1 1 1 1

0

0.5

1

1.5

2

2.5

3

3.5

4

4.5

5

Wor

k R

emai

ning

(h)

Daily Progress

Ideal Progress

Current Trend

Sort Sprint Tasks Update Task Slips

Sprint Tracking & Burndown Charting

Page 31: Project Management Foundations Series Course 104 - Agile Project Management Concepts

The Sprint Review

• The Scrum Team presents the following:• What was accomplished during the sprint• What was not accomplished during the sprint• Any issues encountered during the sprint• Any changes needed during the sprint

• The Scrum Team will demo or showcase the product, feature or other deliverable that was completed at the end of the sprint

• The Sprint Review is an informal meeting with the following rules:

• No more than two (2) hours to prepare

• No slides…No handouts

• Whole team participates

Page 32: Project Management Foundations Series Course 104 - Agile Project Management Concepts

The Sprint Retrospective

• Conducted after every sprint• Entire project stakeholder group should participate:

• ScrumMaster• Product Owner• Scrum Team• Customers, End Users, Senior Leaders and Others

• Discuss how the last sprint went• What is (and is not) working• Issues encountered• Changes needed

Page 33: Project Management Foundations Series Course 104 - Agile Project Management Concepts

Product Backlog Refining

• Assess remaining Product Backlog• Add / Delete / Modify Product Backlog• Re-Prioritize Product Backlog• Start Next Sprint Planning

Page 34: Project Management Foundations Series Course 104 - Agile Project Management Concepts

Applying Agile Project Management To Your

Organization

Page 35: Project Management Foundations Series Course 104 - Agile Project Management Concepts

Making The Transition To Agile

Traditional Project Management Agile Project Management

Focus on plans and document artifacts Focus on customer satisfaction and interaction

Change controlled via formal request process Change is expected, planned and adapted as needed

Resource-intensive up-front planning Progressive, iterative, rolling-wave planning

Sponsor dictated, scope-based delivery Product Owner prioritized, time-boxed delivery

Activity management via work breakdown structure

Task planning and execution flow based on Team Member commitment

Top-down control Collaboration of self-disciplined and self-organizing teams

Rigid, formal management methods Minimal set of loose guidelines and best practices

Page 36: Project Management Foundations Series Course 104 - Agile Project Management Concepts

Adopt key features of the process• Release and Iteration Planning

• Product and Iteration Backlogs

• Tracking via Burndown charts

• Team co-located in team rooms

• Core team dedicated to project

Define allowable actions• Estimation done only by performers

• Prioritization done only by product owners

Prioritize work opportunities • Priorities always decided in Sprint Planning Meetings

Establish and synchronize delivery pace• 4-Week Sprints as a default

Minimize sunk project costs• Sprint Resets or Stops allowable only in extreme circumstances

Tailoring Agile To Fit Your Organization

Page 37: Project Management Foundations Series Course 104 - Agile Project Management Concepts

1. Daily SCRUM Stand-Up Meetingso Follow the three (3) question formato Enforce who is (and is not) allowed to speak at the meeting

2. Team Co-Locationo Common areas to collaborate and meeto Private spaces for thinking and focused work

3. Planning Pokero Fun, card-game based activity to develop work task effort/time estimates

4. Resource Pairingo Team-based work assignments rather than solo efforts/tasks

5. Use a “Scrum Board”1. Great visual management tool!

• Small Release Cycleso Keep sprints under six (6) weeks in lengtho Thirty (30) days is preferred

Agile Project Management Best Practices

Page 38: Project Management Foundations Series Course 104 - Agile Project Management Concepts

Review What You’ve Learned

Page 39: Project Management Foundations Series Course 104 - Agile Project Management Concepts

Course 104 – Introduction to Agile Project Management Concepts

- QUIZ -

Question 1:• The ______________ is

developed and prioritized by the Product Owner.

Page 40: Project Management Foundations Series Course 104 - Agile Project Management Concepts

Course 104 – Introduction to Agile Project Management Concepts

- QUIZ -

Question 1:• The ______________ is

developed and prioritized by the Product Owner.

Answer:Product Backlog

Page 41: Project Management Foundations Series Course 104 - Agile Project Management Concepts

Course 104 – Introduction to Agile Project Management Concepts

- QUIZ -

Question 2:The Agile Manifesto states that agile values individuals and interactions over ________ and ________.

Page 42: Project Management Foundations Series Course 104 - Agile Project Management Concepts

Course 104 – Introduction to Agile Project Management Concepts

- QUIZ -

Question 2:The Agile Manifesto states that agile values individuals and interactions over ________ and ________.

Answer:Process and Tools

Page 43: Project Management Foundations Series Course 104 - Agile Project Management Concepts

Course 104 – Introduction to Agile Project Management Concepts

- QUIZ -

Question 3:True or False.

The definition of Agile Project Management is the Iterative method of determining requirements for engineering and information technology development projects in a highly flexible and interactive manner.

Page 44: Project Management Foundations Series Course 104 - Agile Project Management Concepts

Course 104 – Introduction to Agile Project Management Concepts

- QUIZ -

Question 3:True or False.

The definition of Agile Project Management is the Iterative method of determining requirements for engineering and information technology development projects in a highly flexible and interactive manner.

Answer:True.

Page 45: Project Management Foundations Series Course 104 - Agile Project Management Concepts

Course 104 – Introduction to Agile Project Management Concepts

- QUIZ -

Question 4:• What are the three

questions asked during every Daily Scrum Stand-Up Meeting?

Page 46: Project Management Foundations Series Course 104 - Agile Project Management Concepts

Course 104 – Introduction to Agile Project Management Concepts

- QUIZ -

Question 4:• What are the three

questions asked during every Daily Scrum Stand-Up Meeting?

Answer:1. What did you accomplish yesterday?

2. What are you working on today?

3. What is getting in your way?

Page 47: Project Management Foundations Series Course 104 - Agile Project Management Concepts

Course 104 – Introduction to Agile Project Management Concepts

- QUIZ -

Question 5:• One of the most

important methods for communicating the progress of the sprint is the _______________.

Page 48: Project Management Foundations Series Course 104 - Agile Project Management Concepts

Course 104 – Introduction to Agile Project Management Concepts

- QUIZ -

Question 5:• One of the most

important methods for communicating the progress of the sprint is the _______________.

Answer:Sprint Burn-Down Chart

Page 49: Project Management Foundations Series Course 104 - Agile Project Management Concepts

CONGRATULATIONS!

You have successfully completed:

Project Management FoundationsCourse 103 – Project Stakeholder Management

PRESENTED BY:Think For A Change, LLC.

Page 50: Project Management Foundations Series Course 104 - Agile Project Management Concepts

Please visit: Please visit: http://www.thinkforachange.comhttp://www.thinkforachange.com

For more information on best/next practices, educational training, tools, techniques and process models for:

• Project Management• Innovation Management• Product Management• Leadership