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.
10. Product backlog Is an estimate of system requirements in order of priority. Saying it in a traditional way, it is the project plan.
11.
12. Burndown Chart No work 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 Work being 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 Work being 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 Individual Burndown 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.
17. Sprint backlog Just a part of product backlog that can form a deliverable. Better know as release plan in traditional project management.
18.
19.
20.
Editor's Notes
Hello friends, Today I am here to present on “Agile Project Management with Scrum”. We will learn how Scrum can avoid chaos and disasters in a project life cycle. [Slide Change]
![Agenda ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],We will only be discussing basics about Scrum and activities involved.](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)