The document discusses key concepts in Agile and Scrum project management frameworks. It outlines some common misconceptions about Agile, describes Scrum roles and ceremonies like sprint planning and review meetings, and emphasizes that adopting Scrum requires changes to team dynamics, skills, and work habits.

1. מבט לפרויקט סדרת הרצאות Introduction to Agile & Scrum Elad Sofer - Agile coach http://www.TheScrumster.com [email_address]

3. Changes in basic assumptions 1/2 Division of work to specialized teams (specification, design and testing) is efficient It is possible to “collect” or even “know” all the requirements up-front The harder we plan and analyze in the beginning, the less there’s change in the project and the more successful the project. Multiple parallel programs speed up the development Multiple programs create big management overhead and risk of overloading the pipeline, R&D works most efficiently in continuous mode There is change always and responding to it is vital. Uncertainty is best reduced by learning from actual implementation Requirements evolve as customers’ and our knowledge increases – based on experience Cross-functional teams reduce the amount of handovers and are more productive

4. Changes in basic assumptions 2/2 Product development process can be defined as a predictable and repeatable process Product development is an evolving and adaptive process You can save time by “good-enough” development. Any technical debt will slow development down and thus we don’t allow technical debt to accumulate. It’s possible to transfer information effectively on written documents without much of human contact. Essential knowledge is lost in every handover and human interaction is needed to overcome it. Resource usage and cost optimization is the key to increased productivity Concentrating on value stream optimization, removing waste and sustainable flow increases productivity

5. Wishful thinking No matter how hard you try, it ain’t gonna happen

6. Values

9. Misconceptions Don't believe anything you hear

10. Agile does not mean: No planning No requirement analysis No visibility to end target No documentation No processes No design Hacking

11. Agile development means: Adaptive planning Evolving requirements Good design Sufficient documentation High degree of self-discipline skillful software engineering Adaptive processes

14. Scrum process overview Product backlog Business Vision Customer Sprint backlog Working software Feedback 2-4 weeks 24 hours

16. Product backlog example Backlog item Estimate As a user I would like to register 20 As a user I would like to login 13 As a buyer I would like to make a bid 8 As a buyer I would like to pay with a credit card 20 As a seller I would like to start an auction 20 ... …

17. Burndown chart – project tracking made easy

20. Sprint Backlog - Example As a user I would like to register Code the middle tier (8 hours) Code the user interface (4) Write test fixtures (4) Code the foo class (6) Update performance tests (4)

24. Sequential vs. overlapping development Source: “The New New Product Development Game” by Takeuchi and Nonaka. Harvard Business Review, January 1986. Rather than doing all of one thing at a time... Requirements Design Code Test ...Scrum teams do a little of everything all the time

29. "Scrum is easy..." Ken Schwaber - co-creator of Scrum "... Dealing with the problem it exposes is very very very hard"