How to use Agile Software Development from the first contact with the client to delivering the application

1. / 301

2. / 30
Hello!
NetAnts - Digital productions
info@netants.nl
Produktieweg 1 - Roermond
085-4868840
Aron Beurskens - Founder
aron@netants.nl
06-51791756
https://nl.linkedin.com/in/aronbeurskens
2

3. / 30
Digital productions
Managed hosting
Software development
as a service
Scrum
3

4. / 30
Agile Software Development from Experience
- Why this talk
- Agile Software Development
- Scrum in a few seconds
- Scrum in practice
- Common pitfalls
- What scrum solves
- What scrum does not solve
4

5. / 30
Why this talk
- Scrum is learned by experience
- Many companies use scrum differently
- Many companies mis scrums full potential
5

6. / 30
Agile software development
- Reaction on waterfall
- Iterations
- Communication
- Progress
- Software that works
6

7. / 30
Scrum
7

8. / 30
Lets scrum
- Creating epics
- Global estimations, costs and planning
- Add weights to epics
- Create the team
- Create sprints
- Prepare for the first sprint
- Start sprinting
8

9. / 30
Creating epics
9

10. / 30
Global estimations, cost and planning
10
Epic Estimate Weight Metric Value Team member Hours per week
Epic 1 1152 240 Hours per week 160 Product owner 24
Epic 2 192 40 Weeks per sprint 3 Tester 12
Epic 3 864 180 Hours per sprint 480 Developer 1 36
Epic 4 864 180 Points per sprint 100 Developer 2 36
Epic 5 384 80 Developer 3 36
Epic 6 1344 280 Scrum master 16
Totaal 4800 1000 Totaal 160

11. / 30
Create sprints
11

12. / 30
Add epics weight
12

13. / 30
Product ownerDevelopment team
Scrum master
Create the team
Stake holders
13

14. / 30
Prepare for the first sprint
- Creating the first user stories with the Product Owner
14

15. / 30
Prepare for the first sprint
- Linking user stories to epics
15

16. / 30
Prepare for the first sprint
- The first refinement meeting - how to know weights?
16
User
story 1
User
story 2
User
story 3
User
story 4
User
story 5
1 2 3 5 8 13 20

17. / 30
Prepare for the first sprint
- The first refinement meeting - how to know weights?
17
User
story 1
User
story 2
User
story 3
User
story 4
User
story 5
1 2 3 5 8 13 20

18. / 30
Prepare for the first sprint
- Adding weights
18

19. / 30
Start sprinting
- The first planning meeting
19

20. / 30
Daily stand-up
20
- Max 15 minutes
- Everybody stands
- Report to each other
- No in-depth discussions
- Different methods:
- The 3 basic questions
- Walking the board
- Eliminate impediments

21. / 30
Refinement meetings
21
- 2 times a week 2 hours
- Fixed times in the agenda
- Filling the backlog
- Max 2 sprints ahead

22. / 30
Review meeting
22
- Inform stakeholders with KPI’s
- Inform all about progress
- Give demo about the delivered
- Get feedback from stakeholders

23. / 30
KPIs - velocity
23

24. / 30
KPIs - Bugs
24

25. / 30
KPIs - Stakeholder satisfaction
25

26. / 30
KPIs - Team satisfaction
26

27. / 30
Review meeting
27

28. / 30
Retrospective
28
- Reflect on last sprint
- Reflect on proces
- Reflect on each other
- Create actions!
- Who attends retrospective?
https://www.funretrospectives.com/

29. / 30
Common pitfalls
- Bad user stories
29

30. / 30
Common pitfalls
- Definition of ready
30
* user story has flow diagram
* user story has a design
* user story is completely explained
* user story is can be explained by the development team
* user story is estimated based on weight (story points)
* user story can have 20 story points at maximum
* structure / data is technically described (structure, type, length)
* user story has acceptance criteria (checklist)

31. / 30
Common pitfalls
- Bad user stories
31
https://gitlab.netants.nl/aron/agile-software-development/issues/7

32. / 30
Common pitfalls
32

33. / 30
Common pitfalls
33

34. / 30
Common pitfalls
34

35. / 30
Common pitfalls
- Stakeholder who don’t have/make time
- Product owners who don’t put time in
- Too many user stories in backlog
- Developers who expect others to test
- Stakeholders who don’t respect the PO
- Assuming things are done too easily
35

36. / 30
Common pitfalls
- Definition of Done
36
* user story complies to acceptance criteria
* user story complies to descriptions
* code has been reviewed
* unit tests cover functionality
* feature tests cover functionality
* code has been merged 'master' branch
* ui is validated and approved
* development team has tested and approved user story
* product owner has done a sanity check on acceptance
* functional documentation is updated
* technical documentation is updated
* there is a shippable artifact

37. / 30
What does scrum solve?
- Better quality (responsibility to development team)
- Fast expectation management
- Increase in satisfaction
- Help with focus
- Self organizing teams
37

38. / 30
What does scrum not solve
- Time to market
- Reducing cost
- Lighten team pressure
38

40. / 3040