using tools to make cmmi more agile | bleum
TRANSCRIPT
Using Tools to Make CMMi More Agile
Eric Rongley Bleum
CEO
Bleum is the leading software outsourcer focused on customers and systems that need near zero defect delivery
Bleum
We build high performance teams for
systems that must always run
We help clients methodically improve
the run-time performance of their
mission critical applications
We help software publishers reduce cycle time while improving the quality of their releases
Zero Defect Track Record Making perfect the probable outcome
Our Secret Sauce:
1. Smart teams 2. Senior Management
Commitment 3. Automatic process
control and measurement
Keys to Achieving Zero Defects Routinely
1. Define a process and execute
2. Measure everything – in real time
3. Focus on exceptions – Good and Bad
4. Collect and Use Historical Data
5. Let the data lead you
6. Rinse and Repeat
Define a Process, Any Process and Keep It Simple
Don’t get hung up on “Perfect” Metrics, have multiple views Measure Gates Measure Work in Process
Mine That Data!
Measure Everything
EVERYTHING IS A
TASK
THAT TAKES
TIME
AND HAS SOME
OUTPUT
Use a Real Time Tool
Time tracking to plan better
Static code analysis Capture un-planned
tasks Reduce Escapes!
Focus on Exceptions Good and Bad Governance should make slips visible
Follow the data
A B C D E F G H I J
0%
2%
4%
6%
8%
10%
12%
14%
0
0.2
0.4
0.6
0.8
1
1.2
Mustang Elephant Mongoose Falcon Addax Bison Bear Antelope
Fault Density vs Review Effort % Fault Density Reviewing Effort %
(Secondary Axis)
Rinse and Repeat
Across teams, focus on: Phase Containment
If all you have is a hammer in the toolbox, everything looks like a nail.
- Bernard Baruch
“
”
Agile Throws a Wrench in the Works
Good 1. Teams focus on delivering
valuable functionality 2. Digestible progress keeps
motivation up 3. Continuous integration
helps capture defects 4. Peer pressure to be
productive
Bad 1. Often leads to bad
architectures 2. Tempts bad human nature
not to document and plan 3. Hero dependent 4. Scope creep and schedule
slippages endemic 5. Too much shared
responsibility for Quality, etc
Synthesizing the Best of Agile, CMM & RUP
1. Use Case Survey as the glue that holds together Use Cases and User Stories. Combine the concept of User Stories and Scenarios of Use Cases.
2. Reduce process overhead – Guide to tailoring process to overcome the “Heavyweight” perception of CMM.
3. Prioritize what to elaborate as Use cases and what to keep as User Stories.
4. Automation of metrics collection will reduce the process overhead.
5. Use RUP approach to technical risk by frontloading its resolution.
Use Case ~ Epic Scenario ~ User Story
Using the Right Tool for the Right Job What we see over the course of hundreds of projects
SDLC When to use
Waterfall Smaller projects with non-volatile requirements
Iterative (RUP)
Large production systems with complex requirements
Agile/Scrum Minimum Viable Products Team of senior self directed individuals
Keep Overall Budget and Time Control
Roadmap (use case survey, what is going to be built). Estimate (Time, Salaries, IT Resources). Scope
– Captured and tracked – Keep all aware every time it changes.
Omnipresent will provide the Sprint and Whole project view
to guard against run on projects.
Bleum Releases OmniPresent
Commercial Version of Hydra Beta Version free for next one year http://omnipresent.bleum.com/ See your baseline performance and how your team
compares on other metrics, especially those that utilize code analytics
Agile Lifecycle in Beta
Daily SCRUM Meetings
Sprint Planning
Sprint Demo
Bleum’s Area of Interest
Measuring Productivity Tools for counting function points? Productivity of testing function? Methods of calculating complexity analysis of automated test
scripts?
Eric Rongley CEO [email protected] USA Headquarters 901 Englewood Parkway, STE 106 Englewood, CO 80110 Worldwide Headquarters Cloud-9 Mansion 8F 1118 West Yan 'an Road Shanghai, 200052 PRC Tel: +86 (21) 6282 1122
Thank you
21
Learn more about Bleum at www.bleum.com
Learn more about Omnipresent at omnipresent.bleum.com