The Pragmatic Agilist: estimating, improving quality, and communication with agile values and practices
1 like180 views
The document discusses the challenges and solutions in agile development management, focusing on issues like missed deadlines, recurring bugs, and inefficient communication within teams. It highlights the importance of values, effective estimation, automated testing, and fostering a supportive team environment. Strategies for improving communication, collaboration, and feedback processes are also outlined to drive innovation and predictability in delivering software value.
The Pragmatic Agilist: estimating, improving quality, and communication with agile values and practices
- 1. THE PRAGMATIC AGILISTThiago Colares Chaves Exchange SEBRAE — Belo Horizonte, July 2018
- 2. Hallo! I’M THIAGO COLARES Agile manager Full stack developer Open source Co-founder @ Agilize Cloud Accounting @thicolares
- 3. YOUR TEAM CAN GET MORE DONE BEFORE GROWING TOO BIG
- 4. VALUES
- 6. SPREAD THE WORD itemize give purpose make speeches reinforce with context be a model
- 7. 3 PAINS
- 8. “ 1st pain The dev team always miss deadlines
- 9. WE... always miss planned hours don’t believe in estimates get lost with the unforeseen have low self-esteem
- 10. IMPACT > speed INNOVATION > predictability DELIVER VALUE > arbitrary deadline
- 11. ISSUE TYPES
- 12. Story Minimum software increments that delivers value to the user.
- 14. Chore Task Story Small manual activities. Not a software increment (yet).
- 16. Bug SpikeTask Chore Story Simple program to explore solutions. Inputs for estimation.
- 22. Story Bug Chore Spike Design spike Epic Un known Task We estimate We log the time spent
- 25. STORY POINTS
- 27. 5h20min
- 28. ~8h AMOUNT OF WORK + COMPLEXITY + RISK AND UNCERTAINTY + INNOVATION
- 29. 2 STORY POINT
- 30. 21 3 5 8 FREQUENT RARE
- 31. 21 3 5 8 1 3 2 3 2 3 1 3 2
- 32. ESTIMATING
- 34. Completed stories Average of the last three completed sprints Next sprint’s estimate: Current sprint velocity Incomplete stories
- 36. ➔ Current sprint ➔ Forecast
- 37. ➔ Current sprint ➔ Forecast
- 38. ➔ Current sprint ➔ Forecast VelocityForecast 42 / 1 + 3 = 45 ( 0+ 4+ 7 ) / 3 = 3
- 39. ➔ Current sprint ➔ Forecast VelocityForecast 42 / 1 + 3 = 45 ( 0+ 4+ 7 ) / 3 = 3
- 40. ➔ Current sprint ➔ Forecast VelocityForecast 42 / 1 + 3 = 45 ( 0+ 4+ 7 ) / 3 = 3
- 41. ➔ Current sprint ➔ Forecast 35 / 3 + 4 = 16 ( 4+ 7 + 8 ) / 3 = 6 VelocityForecast
- 42. ➔ Current sprint ➔ Forecast 35 / 3 + 4 = 16 ( 4+ 7 + 8 ) / 3 = 6 VelocityForecast
- 43. ➔ Current sprint ➔ Forecast 35 / 3 + 4 = 16 ( 4+ 7 + 8 ) / 3 = 6 VelocityForecast
- 44. ➔ Current sprint ➔ Forecast 27 / 6 + 5 = 10 ( 7 + 8 + 7 ) / 3 = 7 VelocityForecast
- 45. ➔ Current sprint ➔ Forecast 27 / 6 + 5 = 10 ( 7 + 8 + 7 ) / 3 = 7 VelocityForecast
- 46. ➔ Current sprint ➔ Forecast 27 / 6 + 5 = 10 ( 7 + 8 + 7 ) / 3 = 7 VelocityForecast
- 47. ➔ Current sprint ➔ Forecast 30 / 7 + 6 = 11 ( 8 + 7 + 7 ) / 3 = 7 VelocityForecast Work added
- 48. ➔ Current sprint ➔ Forecast 30 / 7 + 6 = 11 ( 8 + 7 + 7 ) / 3 = 7 VelocityForecast Work added
- 49. ➔ Current sprint ➔ Forecast 30 / 7 + 6 = 11 ( 8 + 7 + 7 ) / 3 = 7 VelocityForecast Work added
- 50. ➔ Current sprint ➔ Forecast 13 / 7 + 7 = 9 ( 7 + 7 + 7 ) / 3 = 7 VelocityForecast Work removed
- 51. ➔ Current sprint ➔ Forecast 13 / 7 + 7 = 9 ( 7 + 7 + 7 ) / 3 = 7 VelocityForecast Work removed
- 52. ➔ Current sprint ➔ Forecast 13 / 7 + 7 = 9 ( 7 + 7 + 7 ) / 3 = 7 VelocityForecast Work removed
- 53. 6 / 7 + 8 = 8 ( 7 + 7 + 6 ) / 3 = 6 VelocityForecast
- 54. 6 / 7 + 8 = 8 ( 7 + 7 + 6 ) / 3 = 6 VelocityForecast
- 55. 6 / 7 + 8 = 8 ( 7 + 7 + 6 ) / 3 = 6 VelocityForecast
- 56. Almost correct!
- 57. IN THE WILD Work completed Work remaining Work added
- 60. “ 2nd pain The bug is still occurng Meta-slide:)
- 61. WE SPENT A LOT OF TIME... fixing bugs silly and recurring ones too struggling on evolving
- 62. RECOVERING FROM BUGS > controlling them
- 64. ● SANITY CHECKS We can’t help ourselves ● IN-HOUSE TALKS Every friday ● AUTOMATED TESTING DOJO Open to the community ● KPI DASHBOARD Geckoboard, Prometheus + Grafana
- 65. ● ERROR MONITORING SOFTWARE Sentry, Rollbar ● CODE STANDARDIZATION PSR Coding standard and Naming conventions ● UNIT TESTS It became a habit ● CODE REVIEW It became a habit ...
- 67. FEAR COURAGE Errors generate learning Courage to err or innovate No unnecessary pressure Team support
- 68. FRIENDLY ENVIRONMENT There are no stupid questions Mutual respect and admiration Questions are welcome There's no room for ego
- 69. COWBOYS SHARED OWNERSHIP Cowboy coders Support team's mastering Make room for improvements
- 71. “ 3rd pain Inefficient communication. Looooooong meetings.
- 72. TRUST > CONTROL
- 73. CONTEXT GENERATES AUTONOMY Communicate sooner Goals, strategies, and metrics Clarify priorities Clear definition of success
- 74. CONTROL AS EXCEPTION Help a newcomer Short-term emergencies Someone in the wrong role
- 75. WIKI
- 76. 909 editions Mutual collaboration 0% orders (just some nudges) The team have asked for this slide 161 pages In a year
- 77. MEETINGS
- 78. Daily meeting 1.5 hour 2 week 24h Planning meeting 1 day or more
- 80. Daily meeting 1.5 hour 30min 2 week 1 week 24h Planning meeting 1 day 1h Retrospective meeting. 1h Backlog grooming (during the sprint) Faster feedback 1-to-1 feedbacks. 15min Criteria acceptance
- 81. PLANNING MEETING Same location, same time Everybody Review velocity Clarify acceptance criteria Negotiate activities Estimate Time-boxed (1h)
- 83. GIVEN Pre-conditions Past tense. Passive voice WHEN Action to be tested (only one) Present tense. Active voice THEN Changes expected after that action Future tense. Passive voice
- 84. USER ADDS ITEM TO CART GIVEN I'm a logged-in User And I visited the Item page WHEN I click "Add item to cart" THEN The quantity of items in my cart will go up And my subtotal should increment And the warehouse inventory should decrement
- 85. DAILY MEETING Same location, same time Everybody Report to the leader Team communication Risk mitigation Time-boxed (30min)
- 86. WALK THE BOARD + ROTATE THE FACILITATOR
- 87. 1-TO-1 FEEDBACK Build strong relationships Address issues beforehand Opportunity to mentor Foster communication
- 88. BEFORE Frequency matters Right Atmosphere Begin the meeting on time
- 89. DURING Remarkable beginning Open-ended questions Address uncomfortable issues Give constructive criticism Work together to find a solution Share your experiences too End on a positive note
- 90. SOME LEADING QUESTIONS “How’s life?” “What’s been most surprising about working on X so far?” “I was thinking I’m .... Should I ….? What do you think?” “What do you think is the most overlooked area of the business?”
- 91. PITFALLS Avoid calling off It’s about the employee, not you
- 92. RETROSPECTIVE MEETING Yes-no past actions Happy Sad Questions New ideas do try Top 3 sadnesses → Actions Time-boxed (30min)
- 93. IMPACT > speed INNOVATION > predictability DELIVER VALUE > arbitrary deadline RECOVERING FROM BUGS > controlling them PEOPLE > processes TRUST > control
- 96. SPECIAL THANKS TO ○ The time and the battle in the wild :) ○ “Extreme Programming Explained: Embrace Change”, Kent Beck ○ “Manifesto for Agile Software Development”, http://agilemanifesto.org/ ○ Teammates at Agilize Cloud Accounting ○ Maurício Vieira, for discussions and insightfulness ○ So many articles and friends that inspire me every day