Overciming Traditional Project Release Reporting with an Agile Approach Focused on Change

1. Overciming Traditional Project Release Reporting with an Agile Approach Focused on Change 2012 Agile Conference 101522096 黃郁哲

2. Outline • Destination • Background • Difficulties • Method

3. Destination • Introduce how the author teach a company’s division that developing software with out agile method to use it.

4. Background • Intergraph is a large software development company focused on developing complex products aimed at professionals. It is made up of two distinct organizations, Intergraph Process, Power & Marine (PP&M) and Intergraph Security, Government & Infrastructure (SG&I).

5. Background • Intergraph PP&M moved their development operation to Scrum starting in December 2007. This effort culminated in the formation of 75 Scrum Teams and our ability to say that everyone who should be on a Scrum team is on a Scrum team. • The author was responsible for the rollout of Scrum in the PP&M division. In 2011 the author moved to the Intergraph SG&I division to take them through the process of change.

6. What makes the change a big issue • Scrum / agile reporting are based on delivery of value. Traditional reporting is based on effort expended. • Not supplying better templates to produce the information required. This led to confusion when teams wanted to do release reports since they virtually had to learn how to do it themselves.

7. Principles of Reporting

8. Principles of Reporting • Report the Changes • Make everything Available to Everyone • Make Sure the Backlog includes Everything • Make it Simple • Use the Same Reports for all Levels of the Organization

9. Five useful report

10. Five useful report • Burn-up chart • Scope change report • Epic progress report • Investment Allocation report • Project Allocation report

11. Thanks for listening