20
Ariel Schapiro Agile PMO ”improving projects health”

Agiles 2009 - Agile PMO

Embed Size (px)

DESCRIPTION

Many companies nowadays had embraced agile practices in their core methodologies and are seeing improvements in the way they manage expectations with their customers or in their product quality as well. Is there anything left to achieve in the path of continuous improvement? Followed by Lord Kelvin’s famous quote "If you can’t measure it, you can’t improve it.", Ariel Schapiro, PMO at Southworks, will introduce a process that helped him on measuring project’s health with Key Performance Indicators focused at improving a service-based business. This scenario usually requires more measurements than velocity, burndown and burnup charts in order to enhance aspects of the projects such as the daily work organization, awareness of the big picture, knowledge sharing and progress-seeking spirit. Ariel will explore the process in which these indicators are measured and its incremental nature. Also how PM’s from different teams are collaboratively engaged on this engineering approach on agile practices. As corollary, a statistical analysis will help on drawing the conclusions of the efficiency of this process. Target audience: Scrum practitioners, PMO members, project managers, developers and process owners Key benefits: - Understand indicators beyond velocity, burndown and burnup in order to measure project’s performance in service-based businesses. - Get a sense of the application of engineering practices to agile contexts.

Citation preview

Page 1: Agiles 2009 - Agile PMO

Ariel Schapiro

Agile PMO”improving projects health”

Page 2: Agiles 2009 - Agile PMO

Context

Health Check measurement

process

Results & Conclusions

Q&A

Plan

¿?

Page 3: Agiles 2009 - Agile PMO

CONTEXT

Page 4: Agiles 2009 - Agile PMO

Southworks.NET

ISO 9001:2000

x 4

Page 5: Agiles 2009 - Agile PMO

Projects

Reference implementation applications

.NETTraining Kits

Hands on labsSaaS (S+S)

WCF

WFSilverlight

Identity Windows Azure

WPF

Page 6: Agiles 2009 - Agile PMO

SCRUM-like Process

Iteration Backlog

Customer participation

Weekly meetings schedule

(2~3 months total duration)

TDD

Pair Programming

Page 7: Agiles 2009 - Agile PMO

Continuous Improvement

Page 8: Agiles 2009 - Agile PMO

HEALTH CHECKMEASUREMENT PROCESS

Page 9: Agiles 2009 - Agile PMO

Anatomy of the process

Formal Process(ISO, CMMi)

Hard Indicators

Customer feedback

Retrospective Services

Page 10: Agiles 2009 - Agile PMO

Hard IndicatorsTeam self assesment

based on thresholds

and backed up by evidence.

Page 11: Agiles 2009 - Agile PMO

Hard Indicators

Hard Indicators

Page 12: Agiles 2009 - Agile PMO

RetrospectiveServices

Retrospective Services

•Good…•Poor…•Consider…

Page 13: Agiles 2009 - Agile PMO

Customer feedback

Customer feedback

Page 14: Agiles 2009 - Agile PMO

Anatomy of the process

Formal Process(ISO, CMMi)

Hard Indicators

Customer feedback

Retrospective Services

Page 15: Agiles 2009 - Agile PMO

RESULTS &CONCLUSIONS

Page 16: Agiles 2009 - Agile PMO

Results

Age (weeks)

Page 17: Agiles 2009 - Agile PMO

Results

Page 18: Agiles 2009 - Agile PMO

Results

"The project map helped me to understand the global scope of the project and to know easily

what are we working on right now.“

“These assets really help me on planning ahead the testing process."

"Screencasts were and still are very useful for me to go over the progress made during the sprint.“

Page 19: Agiles 2009 - Agile PMO

Conclusions

• Improvement because of:– Self measurement: reflecting– Osmotic communication (Alistair Cockburn) at a

company level• Scrum + engineering practices• Valuable initiatives imitation• Sharing + Reusability

Page 20: Agiles 2009 - Agile PMO

Thanks!

Ariel [email protected]

http://blogs.southworks.net/aschapiro/