Agile Project Management with Scrum

Slide 1: Agile Project Management with Scrum By Aditya Raj

Slide 2: Agenda We will only be discussing basics about Scrum and activities involved. • What is Scrum? • Cost of change in Scrum • Scrum roles • Scrum activities • Process flow • Project Backlog • Burn down chart • Sprint Backlog • Need to remember • Credits

Slide 3: What is Scrum Scrum is a simple approach for managing complex projects. • Based on common sense • Less documentation • Release early, release often • Avoid chaos • Better level of communication • Commitment oriented • Agile in nature and practice Scrum in practice:

Slide 4: Cost of change in Scrum Scrum is flexible enough to accommodate changes easily to requirements without incurring any additional cost. Waterfall • Scrum allows changes at any point • But not in a release cycle Cost of change • Scrum expects changes would come up and stays prepared for them Development Life Cycle Cost of change Scrum Development Life Cycle

Slide 5: Scrum roles Scrum makes clear distinction between committed members and interested members of a team. • Product owner – Customer representative – Prioritizes product requirements • Team – Develops product – Responsible for failure or success – Self managed and organized • Scrum Master – Teaches and implements Scrum – Ensures Scrum is practiced properly – Maintains documentation required

Slide 6: Scrum activities Scrum process is all about clarity, inspection and adaptation. • Sprint planning meeting – Before every Sprint – Divided in two half for focusing on what to do and how to do • Sprint – Release cycle of 2 to 4 weeks – No changes accepted while in Sprint • Daily Scrum ? – Daily meeting during Sprint for about 15 minutes ?? – Every member answers: • What they did since last meeting? • What they plan to do till next meeting? • What obstacles are there in their way? Continued…

Slide 7: Scrum activities Scrum process is all about clarity, inspection and adaptation. • Scrum review meeting – Is done after every Sprint – To demonstrate that is being done – And give feedback • Scrum retrospective meeting – Is done at end of every Sprint after review meeting – To discuss experiences and problems faced to improve further – The product owner is not required to attend this meeting

Slide 8: Process flow Scrum process flow is iterative and incremental in nature. As it is a light weight process, it results in better performance. 15 mins Daily Scrum Meeting Sprint Backlog tasks 30 days Sprint Backlog distributed by team Potentially Shippable Product Increment Product Backlog As prioritized by Product Owner Source: Agile Software Development with Scrum by Ken Schwaber and Mike

Slide 9: Product backlog It is an estimate of system requirements in order of priority. Saying it in a traditional way, it is the project plan. • Same as Project plan • Monitors entire project • Prioritized to get faster ROI and better results • Prepared and managed by product owner • Requirements can be added at any point • Sweet and simple, easy to manage

Slide 10: Product backlog Is an estimate of system requirements in order of priority. Saying it in a traditional way, it is the project plan.

Slide 11: Burndown Chart Is an early warning indicator which tells progress of project and individuals very clearly. Quite similar to Gantt charts. • Helps in predicting problems • Helps in performance appraisals • Works like an overall tracker • Useful for evaluating overall performance

Slide 12: Burndown Chart Is an early warning indicator which tells progress of project and individuals very clearly. Quite similar to Gantt charts. No work being done Work done Days in Sprint

Slide 13: Burndown Chart Is an early warning indicator which tells progress of project and individuals very clearly. Quite similar to Gantt charts. Work being done but not very fast Work done Days in Sprint

Slide 14: Burndown Chart Is an early warning indicator which tells progress of project and individuals very clearly. Quite similar to Gantt charts. Work being done but not very fast Work done Days in Sprint

Slide 15: Burndown Chart Is an early warning indicator which tells progress of project and individuals very clearly. Quite similar to Gantt charts. Individual Burndown chart Work done Days in Sprint

Slide 16: Sprint backlog Just a part of product backlog that can form a deliverable. Better know as release plan in traditional project management. • Product requirement that will be covered in a sprint • A real time picture of work in a sprint • Avoids problems that may delay or fail a release • Doesn’t allow any additions • Can only be modified by team

Slide 17: Sprint backlog Just a part of product backlog that can form a deliverable. Better know as release plan in traditional project management.

Slide 18: Need to remember Yes back to where we started. What is Scrum? • Few important facts to always remember about scrum – Is common sense – Is not a solution to every problem – Is an approach towards software development – Is very fast and flexible – Is commitment oriented – Is based on clarity, inspection and adaptation – Implementing scrum takes time (nothing such as big bang)

Slide 19: Any questions • There I can see a bulb on your head. – Go on and ask the question, I don’t have a magic marker  You may also mail me your queries or suggestions at: aditya.internet@gmail.com

Slide 20: Credits • Special thanks to – Ken Schwaber for writing such a lovely book Agile project management with Scrum – Michael Vizdos of www.implementingscrum.com For allowing to use there cartoons in presentation. – Hirotaka Takeuchi for The New New Product Development Game