Reclaiming AgileThe Tapestry of Trust in Software CraftsmanshipBarry S. StahlSolution Architect & Developer@bsstahl@cognitiveinheritance.comhttps://CognitiveInheritance.com |
 |
Favorite Physicists & Mathematicians
Favorite Physicists
Other notables: Stephen Hawking, Edwin Hubble |
Favorite Mathematicians
Other notables: Daphne Koller, Grady Booch, Evelyn Berezin |
Some OSS Projects I Run
- Liquid Victor : Media tracking and aggregation [used to assemble this presentation]
- Prehensile Pony-Tail : A static site generator built in c#
- TestHelperExtensions : A set of extension methods helpful when building unit tests
- Conference Scheduler : A conference schedule optimizer
- IntentBot : A microservices framework for creating conversational bots on top of Bot Framework
- LiquidNun : Library of abstractions and implementations for loosely-coupled applications
- Toastmasters Agenda : A c# library and website for generating agenda's for Toastmasters meetings
- ProtoBuf Data Mapper : A c# library for mapping and transforming ProtoBuf messages
http://GiveCamp.org
Agenda
Metrics
- When and Why We Use Them
Ceremonies
- When and Why We Perform Them
Tools & Technologies
- When and Why We Implement Them
Metrics
Velocity Metrics Are Not For You!
Ways to Calculate Velocity
|
|
Story Points ≠ Time
|
|
What Are Story Points Good For?
|
|
Retrospective Red Flag
|
"We need to get better at estimating our work" |
Test Coverage Metrics are not for You!
Good Coverage ≠ Good Tests
Good Unit Tests Give Us the Confidence to Refactor Ruthlessly
Unit Testing only the Happy Path
Metrics
- Velocity Metrics are not for you
- Test Coverage Metrics are not for you
Technical Debt - You Own It!
Technical Debt
|
|
Failure to Manage Tech Debt
|
is managing for the short-term
|
Tech Debt is Real $
|
|
Metrics Take-Aways
- For the Dev Team to help themselves get better
- Not for you to use to judge the team
- Be Careful How You Use
- Velocity
- Test Coverage
- Be Dilligent With
- Technical Debt
Ceremonies
When and Why we Perform Them
Stand-Up Meetings are Not For You
Daily Stand-Ups
Devs making commitments to each other
Daily Stand-Ups
About Exposing Problems Quickly
Stand-Ups are Not
About Gathering Intel for Your Status Report
Iteration Planning Meetings are Not For You
Planning Meetings
About Understanding Stories
Planning Meetings
About Exploring Hidden Complexity
Planning Meetings are not
About Stuffing in Work
Ceremonies
- Stand-Up Meetings are not for you
- Iteration Planning Meetings are not for you
Retrospectives - You Own the Failures
Retrospectives
Retrospectives
Keep It Secret
Keep it Safe
Ceremonies Take-Aways
- For the Dev Team to help themselves get Better
- Not for you to use to report up the chain
- Be Careful How You Use
- Stand-Up Meetings
- Planning Meetings
- Be Dilligent With
- Overcoming Roadblocks
Tools & Technologies
When and why we use them
Task Boards are not for You
Who Needs an E-Board?
Task Board Purpose
|
|
Friction for Developers
|
|
Prototypes & Research Spikes are Not for You
Spike
A Story used to reduce or eliminate unknowns in other stories
...the simplest thing we can program that will convince us we are on the right track... - Ward Cunningham
Prototypes & Spikes
Tools & Technologies
- Task Boards are not for you
- Prototypes & Spikes are not for you
Trust is Yours to Build or Destroy
Trust & Safety
|
|
Estimates
Are Always Lies
Deadlines
|
|
Self Directed Teams
Make their own decisions
Call To Action
Use Retrospectives to create an environment of Trust for our teams
Eliminate anything from our process that doesn't lead to:
- Increasing value to our users
- Decreasing Total Cost of Ownership of our systems