Certified Scrum Developer

Slide of the summary of my experience in CSD course. This slide contains my personal summation on what should the development team focus on when using Scrum methodology for software development.

1. C E R T I F I E D S C R U M D E V E L O P E R
2. Poohdish Rattanavijai thisisrobg@gmail.com https://plus.google.com/+RobGThai/
3. C O U R S E O B J E C T I V E S • To feel the difference between traditional and an agile team • To understand the responsibilities of team. • Understand and experience each scrum activity. • Applying team, technical, and agile techniques when appropriate.
4. C O U R S E S T R U C T U R E • Five-day sprints ideal simulation. • One team, one product, ten people. • Learning practices, techniques and using them. • Review, Scrum, Lecture, Workshop, rinse repeat.
5. M A K I N G O F T H E P R O D U C T M A I L G U • Countless requirements. • Five specified. • One Deliver.
6. S P E C I F I C AT I O N B Y E X A M P L E A C C E P TA N C E T E S T D R I V E N D E V E L O P M E N T Example Test Requirement • Example elaborate Requirements • Use example to create Test • Tests then verify requirement
7. S P E C I F I C AT I O N P Y R A M I D
8. A LWAY S PA I R I N G PA I R P R O G R A M M I N G
9. H O W T O D O I T ? • Two people per machine. • Active person: Think aloud. • Passive person: Ask question. • Always have large piece of papers at hand. • Find mutual agreement on pairing rules , when to do it?
10. A U T O M AT E D B U I L D • Repeating stuff is boring. • Just like tongue twister, the more you do it the more prone to error it becomes. • Takes too much time. • Convenient
11. T O O L S • Choosing the right tool for the right job. • Learn what the tool offer.
12. D E F I N I T I O N O F D O N E • Ensure integrity of the product. • Agreed at the start. Keep your promise. • The more task undone, the more debt you are in. • Keep extending for improvement.
13. S P R I N T A N AT O M Y H E R E ’ S H O W S P R I N T L O O K S
14. S P R I N T P L A N N I N G • Part 1 • Select backlog items to proceed. • Clarify any unclear conditions. • Part 2 • Roughly estimate item size. • Create initial design. • Pick item to generate tasks. • Commit on the tasks. • Time-box.
15. S P R I N T F O R E C A S T • Forecast after Part 2. • Forecast to deliver as agreed upon by giving it all. • Take it seriously. • “Priority” happens all the time. Sometime it’s ok to deliver lower than promised.
16. D E S I G N P R I N C I P L E S • Modularity • You ain’t gonna need it • Inspect and adapt • Design from user perspective • There is no common sense
17. T E S T- D R I V E N D E V E L O P M E N T • Keep it short • Incremental • Keep disciplined • Red, green, refactor • Smell the code • Only one thing at a time
19. C O L L E C T I V E C O D E O W N E R S H I P • Everyone shares responsibility for the quality. • Expects everyone to fix any problems they find. • Anyone can make necessary change anywhere.
20. C O N T I N U O U S I N T E G R AT I O N • Not about the tools. • Strive to make small change. • Strive to get fast feedback. • Discipline to integrate frequently.
21. T E A M • 7±2 for optimal size. • Have complimentary skills. • Help one another. • Share responsibility. • Distributed leadership. • Resolution of conflicts. • Authority to do what is needed to meet commitment.
29. C R A F T S M A N S H I P
33. Q & A