Communicating Agile Project Status - ASPE Training Status to... · Distribution without express permission is forbidden 5 Common Project Failures 1.Going over budget, but not knowing

Management

Presented by:

and

CommunicatingAgile

Project Statusto

1Wednesday, April 10, 13

Copyright 2013 Davisbase LLC. Distribution without express permission is forbidden

• Bill Gaiennie, Davisbase Consulting• 17 years in software development.

• 7 years working with software development teams, training, leading, and coaching Agile teams.

Introduction and Agenda

‣ Agenda‣ What are we focused on with Agile?

‣ How is our approach different with Agile?

‣ How do we communicate status?

‣ Your Next Steps. Q & A.



Start Using Agile:

www.dilb

ert.c

omsc

otta

dam

s@ao

l.com

Copyright 2007 Scott AdamsPrinted November 26, 2007


http://www.dilbert.com





What Does Agile Focus On

Individuals and interactions over processes and toolsWorking software over comprehensive documentation

Customer collaboration over contract negotiationResponding to change over following a plan

http://agilemanifesto.org/

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

We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:

The Agile Manifesto





Agile is Value Driven

PlanDriven

Value/VisionDriven

Requirements

Cost Schedule

Cost Schedule

Features

Predictive Process(Waterfall)

Adaptive Process(Agile)

Constraints

Estimates

The plan createscost/schedule estimates

The vision createsfeature estimates



Why Does Management Need Status?

• Ensure we on schedule

• Ensure we are on budget

• Help tackle problems early

• Make sure we are building the right product

• Make sure we are building the product right

T H E B O T T O M L I N EAVOID A FAILED PROJECT!



5 Common Project Failures

1.Going over budget, but not knowing until past “point of no return.”

2.Extending beyond the original deadline, but not knowing until panic decisions and panic actions are required.

3.Delivering exactly what was asked for, but resulting in something the customer doesn’t need.

4.A pyrrhic victory.

5.Completing a project that should have been cancelled due to “sunk cost” mentality.



Agile vs. Waterfall



Agile vs. WaterfallStatus? Status? Status? Status? Status? Status?



Agile vs. WaterfallStatus? Status? Status? Status? Status? Status?

Surprise?

NOSurprises



If Not Status, Then What?

Managers should have three items of focus during the transition period to Agile:

1. Define the Vision & the Strategy needed to achieve the vision.

2. Remove obstacles that nobody else can remove.

3. Trust the team to get their work done (there will be plenty of opportunities to check their progress.)



How Executives Can Help the Team

1.Ability to Manage and Deal With Risk

2.Results Oriented

3.High Energy

4.Team Player

5.Multitasking Ability

6.Improvement Oriented

7.Listen First, Speak Second

7 Traits of a Highly Effective Executive:



What About Teams?

Agile Teams also have three responsibilities as part of any Agile effort.

1) Collaborate & Communicate

2) Remove obstacles they can remove themselves.

3) Get the work completed that they have committed to.



Is The Team Being Effective?

1. The team embraces the truth

2. The team works in a culture that supports learning

3. The team has the authorityand makes regular decisions

4. The product owner is consistently available to theteam and the team takesadvantage of it

5. The team has a GREAT ScrumMaster



Is The Team Being Effective?(Continued)

6. The team meets daily and is aware of current & upcoming projects

7. Everyone required attendsregular Agile Meetings

8. The team effectively uses theretrospective to inspect & adapt

9. The team has set the rulesand understands thedefinition of done

10. The team is accountable for the work they commit to and they take that commitment seriously



Establishing Trust:

• Management needs to work to empower Agile teams and show them that they trust in their ability to create quality solutions in a timely manner.

• Teams need to trust in the vision of the product owner as well as upper management. Their leaders have a strategy planned to execute the vision in the form of a clearly defined product backlog.

• Established trust is critical to the success of Agile Projects.



Analyzing the 5 Levels of Planning

Project / Product DetailsDaily Planning

Iteration Planning

Release Planning

Roadmap Planning

Vision Planning40,000

30,000

20,000

10,000

Ground



Do The Executives Have Vision?

• To what detail should the Executive team be involved in the day to day operational issues of a project?

• Does the team have an achievable strategy to execute the vision?

• Can executives still feel in power by not using a command and control approach?



Executives & Managers:

• Executives & managers have the primary goal of focusing on the vision & the strategy.

• One common point of failure happens when management dives too deep into the day to day activity of the core team.

• Realistic expectations should be set for this group.

• Ultimately executives should foster top down support with regard to Agile adoption.



Agile Project Reporting:

‣ The best status comes from a demo of working product.

‣ We should strive to minimize intra-sprint reporting.

‣ What gets measured gets done!

‣ Make it big and visible.



Agile Project Reporting:

‣ Possible metrics could include: ‣ Current burndown chart(s)

‣ Sprint goals & changes to the goals

‣ Defects - inflow, outflow, & number of open defects per week

‣ Build quality per day / week

‣ Number of tests automated / tests passed per day or week

‣ Velocity over the last X sprints

‣ Action items, impediments, risks

‣ Customer satisfaction



No One Perfect Path

• Listen to your manager, understand what they need and why

• Align metrics to what you want to see change or improve

• Provide the leanest reporting thatmeets the objectives

• Conversation overdocumentation

• Value intent overprocess



‣ Find experts that can point you in the right direction.

‣ Recognize that training is the proper foundation on which team’s build.

‣ It takes time to get good at anything, Agile is no exception, but the rewards are well worth it.

‣ Getting started is easier than you might think.

Your Call To Action


Your Questions, My AnswersNote: For those questions we do not have time to answer during the webinar, I will be providing a written response.


Documents

Communicating Agile Project Status - ASPE Training Status to... · Distribution without express permission is forbidden 5 Common Project Failures 1.Going over budget, but not knowing