integrating quality into portfolio management
DESCRIPTION
Traditionally, projects are managed based on cost, schedule, and scope. This has lead to poor outcomes, unsustainable development efforts, quality issues, and less than ideal software in terms of value to its users. Our talk will go into how organizations can integrate quality and value considerations into their portfolio management strategies to have a more holistic view leading to less surprises and more valuable outcomes. The talk will go into detail about how Agile plus traditional Earned Value Management (EVM) alongside Managing Software Debt can give a more holistic view of the project portfolio.TRANSCRIPT
Integrating Quality into Portfolio Management
Brent BartonChris Sterling
© 2009-2010,
Brent Barton - Sterling Barton, LLC
Partner, Sterling Barton, LLC
Former CTO. Active Agile Coach, Mentor, Certified Scrum Trainer
More than 15 years software development in many roles as both employee and consultant for organizations from small start ups to multinational corporations
Actively involved in Agile Rollouts from small Product companies to very large IT organizations
Scrum Articles
“AgileEVM – Earned Value Management in Scrum Projects”, IEEE
“Implementing a Professional Services Organization Using Type C Scrum”, IEEE
“Establishing and Maintaining Top to Bottom Transparency Using the Meta-Scrum”, AgileJournal
“All-Out Organizational Scrum as anInnovation Value Chain”, IEEE
2
Email: [email protected]: www.sterlingbarton.com
Blog: gettingagile.comFollow me on Twitter: brentbarton
© 2009-2010,
Chris Sterling – Sterling Barton, LLC
Partner, Sterling Barton, LLC
Consults on software technology, Agile technical practices, Scrum, and effective management techniques
Certified Scrum Trainer
Innovation Games® Trained Facilitator
Open Source Developer
Software architecture consulting for Agile Teams:
Continuous Integration
Source Code Monitoring
Release Management
Design techniques
3
Email: [email protected] Web: http://www.sterlingbarton.comBlog: http://www.gettingagile.com
Follow me on Twitter: @csterwa
© 2009-2010,
Meet Earl - Strategic Planner
Earl just finished the annual portfolio budgeting process for the new fiscal year
© 2009-2010,
Meet Geoff -“Project Manager”
Geoff was a Software Developer
and is now in charge of Saturn
Saturn is a key part of a company-wide strategy
© 2009-2010,
Portfolio is Done for the year! (Today is the beginning of our new Fiscal Year)
© 2009-2010,
Later, Some things aren’t looking as good
© 2009-2010,
[Pause for enlightening discussion]
© 2009-2010,
Defect Containment is helping...not solving
© 2009-2010,
So...what is happening? Who is affected?
© 2009-2010,
Continuous Integration
© 2009-2010,
Meet Huang -Test Engineer
Huang is a Software Development Engineer in Test - SDET
Huang wants to proud of the quality of every release
How can I help?
© 2009-2010,
© 2009-2010,
[Pause for enlightening discussion]
© 2009-2010,
Meet Earl - Strategic Planner
How do I balance Value and Quality?
© 2009-2010,
Balancing Signal Indicators - (some weaker than others)
Value
Quality Constraints(Schedule, Cost, Scope)
Source: Jim Highsmith
© 2009-2010,
[Pause for enlightening discussion]
© 2009-2010,
Meet Sonia - Program Manager
Sonia is a Program Manager
Uses Scrum well...good servant leader
How can I help ensure better
Quality?
© 2009-2010,
Definition of Done
Defines the work products that will be delivered with each item as it is ready for acceptance
Typical entries in Definition of Done
Code includes unit tests, reviewed, checked in
Tests described and executed
Build, release notes
Compliance documentation updated to include current functionality
What else?19
© 2009-2010,
Definition of Done as a Compliance Checklist
Acceptance defined criteria for each user story
Unit tests written and passed
Code compiles with no errors and no warnings
New code doesn’t break existing code
Test case review (Dev to review test case written)
Architectural impact assessed and artifacts updated if necessary
Comments in code
Error codes added
Code reviewed by peer
Code checked in with reference to US#/Task#
Tested on FE
Integration test written & passes
Test code reviewed
Environment requirements documented
Interface document updated/added and checked in to SVN
Acceptance criteria verified complete
All P1-P3 bugs for the story are closed
Test approves user story
Story demonstrated to product owner and accepted on Target Platform
© 2009-2010,
How does a “Release Definition of Done” help?
Every release should have clear quality criteria
With a “Release Definition of Done” you can understand targets better
Measure the gap between the teams’ Definition of Done and a Release Definition of Done.
This gap is a source of quality issues and represents significant risk to schedule
© 2009-2010,
[Pause for enlightening discussion]
© 2009-2010,
I think we’re “done”