Introducing Agile
•
0 likes•239 views
A quick and basic introduction to Agile and I've derived my own agile processes from the first principles.
Report
Share
Introducing Agile
- 1. Introducing Agile Session on Agile
- 2. Genesis of Waterfall Industrial revolution (Design once and Manufacture thousands) Plan - Document - More detailed document - Build - Test - Release - Sell Hierarchy of intelligence (Smart people plan, less smart people manage, dumb people execute efficiently)
- 3. Why Agile? Distributed intelligence Dynamic world Unusable software Less efficient process (Non useful output/overheads - documents that never get read)
- 4. Agile manifesto People and interaction over Process Software versus Document Collaboration versus Negotiation Response to Change versus Following a plan
- 6. Whose Responsibility What is product success? Whose responsibility is it? - Everyone’s (And that makes Agile hard)
- 7. Terms Product Backlog Sprint Sprint Backlog User stories Epics Story Points
- 8. Ceremonies Backlog grooming Sprint Planning Daily Standup Sprint Review/Release Sprint Retrospective
- 9. Focus Definition of done Created by the whole team - (PO) No change in Sprint Backlog - (SM) Ensure discipline and Protect team - (Team) Deliver Sprint
- 10. Estimation: Story points What is Points? Why Points? - A relative measure instead of time estimates. Exercise - Planning Poker
- 11. Retrospective Fault finding in front of a mirror Typical Reasons: - No/Delayed Communication - Bad Specs - Oversight - Bad discipline
- 12. How I’ve turned around 15 night-outs to 1 Reduce Rework - (reduce Reopening tickets) Reduce Scope Change - (no change in middle of sprint) Improve Quality - (reduce Post Production Issues) ● Design Prototypes ● PM Checklists, Checkpoints ● Dev Checklists, Tools (Raygun, Sonarqube, Allure) ● QA Estimates Contextually Derived processes*
- 13. Processes are DIY Don’t copy - Derive your own Processes are mostly inefficient - Evolve them Processes are transient - Let go of them!
- 14. Thanks