Agile Project Management with Scrum

Agile Project Management with Scrum

• 1.
  Agile Project Managementwith Scrum By Aditya Raj
• 2.
  Agenda What isScrum? Cost of change in Scrum Scrum roles Scrum activities Process flow Project Backlog Burn down chart Sprint Backlog Need to remember Credits We will only be discussing basics about Scrum and activities involved.
• 3.
  What is ScrumBased on common sense Less documentation Release early, release often Avoid chaos Better level of communication Commitment oriented Agile in nature and practice Scrum is a simple approach for managing complex projects. Scrum in practice:
• 4.
  Cost of changein Scrum Scrum is flexible enough to accommodate changes easily to requirements without incurring any additional cost. Scrum allows changes at any point But not in a release cycle Scrum expects changes would come up and stays prepared for them Scrum Development Life Cycle Cost of change Waterfall Development Life Cycle Cost of change
• 5.
  Scrum roles Productowner 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 Scrum makes clear distinction between committed members and interested members of a team.
• 6.
  Scrum activities Sprintplanning 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? Scrum process is all about clarity, inspection and adaptation. ? ? ? Continued…
• 7.
  Scrum activities Scrumreview 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 Scrum process is all about clarity, inspection and adaptation.
• 8.
  Process flow Source: Agile Software Development with Scrum by Ken Schwaber and Mike Beedle. Scrum process flow is iterative and incremental in nature. As it is a light weight process, it results in better performance. Product Backlog As prioritized by Product Owner Backlog tasks distributed by team Potentially Shippable Product Increment 15 mins Daily Scrum Meeting Sprint Backlog 30 days Sprint
• 9.
  Product backlog Itis 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
• 10.
  Product backlog Isan estimate of system requirements in order of priority. Saying it in a traditional way, it is the project plan.
• 11.
  Burndown Chart Isan 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
• 12.
  Burndown Chart Nowork being done Is an early warning indicator which tells progress of project and individuals very clearly. Quite similar to Gantt charts. Days in Sprint Work done
• 13.
  Burndown Chart Workbeing done but not very fast Is an early warning indicator which tells progress of project and individuals very clearly. Quite similar to Gantt charts. Days in Sprint Work done
• 14.
  Burndown Chart Workbeing done but not very fast Is an early warning indicator which tells progress of project and individuals very clearly. Quite similar to Gantt charts. Days in Sprint Work done
• 15.
  Burndown Chart IndividualBurndown chart Is an early warning indicator which tells progress of project and individuals very clearly. Quite similar to Gantt charts. Days in Sprint Work done
• 16.
  Sprint backlog Productrequirement 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 Just a part of product backlog that can form a deliverable. Better know as release plan in traditional project management.
• 17.
  Sprint backlog Justa part of product backlog that can form a deliverable. Better know as release plan in traditional project management.
• 18.
  Need to rememberFew 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) Yes back to where we started. What is Scrum?
• 19.
  Any questions ThereI 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: [email_address]
• 20.
  Credits Special thanksto 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