This document provides an introduction to agile and scrum methodologies. It discusses how scrum is suited for projects with unknown requirements and timelines where functionality cannot be fully predicted upfront. Scrum uses short iterations to deliver working software frequently, which allows requirements to evolve based on feedback. It also emphasizes limiting work in progress, cross-functional teams, and regular planning sessions to continuously improve productivity. The product owner is responsible for translating customer needs into requirements for the development team to implement in each sprint.

1. Introduction to Agile
and Scrum
Andrej Koelewijn
@andrkoel
andrej@koelewijn.net

2. Introduction to Agile
and Scrum
First why...

3. Introduction to Agile
and Scrum
First why...
Then how

4. Two types of projects...

9. Manufacturing

11. Managing these requires a
different approach

12. Functionality is known,
Time and resources
can be predicted

15. Do we know this is the right design?

16. Do we know this is the right design?
Do we know how to get the required performance?

17. Do we know this is the right design?
Do we know how to get the required performance?
Do we know all our platforms work as expected?

18. Do we know this is the right design?
Do we know how to get the required performance?
Do we know all our platforms work as expected?
Do we really know what the end-user wants?

19. Do we know this is the right design?
Do we know how to get the required performance?
Do we know all our platforms work as expected?
Do we really know what the end-user wants?
Is the useability good enough?

20. Do we know this is the right design?
Do we know how to get the required performance?
Do we know all our platforms work as expected?
Do we really know what the end-user wants?
Is the useability good enough?
Do we know what the competition will do?

22. With so many unknowns,
you can't predict
functionality, time and resources

23. Better approach:
Do as much as possible within
fixed time and with fixed resources

24. How do you make sure you can deliver...
?

25. How do you make sure you...
?

26. How do you achieve highest...
?

27. Work on limited number
of features at a time...

29. Whenever you run out of time
or money,

30. You have the most important
features releasable...

31. Limit Work in Progress

33. How do you maximize
knowledge creation?

34. How do you maximize
knowledge creation?
Trail and error is how you do it...

39. The faster you can iterate through plan-do-check-act...

40. The faster you can iterate through plan-do-check-act...
The faster you learn

47. How do you improve productivity?

48. How do you improve productivity?
By removing handovers and queues...

55. Scrum
Limit work in progress,
order requiments,
enable learning through feedback,
increase productivity by using a
single cross-functional team

57. Scrum :
By Product Managers
For Product Managers

58. The product manager...

59. The product manager...
Is responsible for Translating
Customer needs...

60. The product manager...
Is responsible for Translating
Customer needs...
Into successful products

61. Product manager (owner) uses
Scrum to manage interaction with
Product development team

62. The product owner translates user needs
into product vision and requirements

63. Team needs to be able to quickly estimate
relative size of the requirments...

64. Team continuously keeps track of productivity,
So amount of work doable in an iteration can be estimated

65. Team needs to keep track of progress in a sprint,
Team needs to regularly release working software...

66. Product owner can regularly test working software
And use feedback to update list of requirements

67. Example of 3 iterations...

100. All team members participate during planning poker session...

101. Taskboard to keep track of progress within one iteration

121. Introduction to Agile
and Scrum
Andrej Koelewijn
@andrkoel
andrej@koelewijn.net