Professional Documents
Culture Documents
Agile Presentation PDF
Agile Presentation PDF
2.Scrum is:
Lightweight because it has few prescribed elements
i) Three roles: Team, Scrum Master (often a Project Manager), Product Owner
ii) Four meetings: Sprint Planning, Daily Scrum, Review,Retrospective
iii)Four artifacts: Product Backlog, Sprint Backlog, Burndown chart , Impediment
Backlog.
1.Goals
2.Activities
3.Values
4.Principles
5.Practices
1.The Goal of XP is to produce High Quality Software.
2.XP attempts to reduce the cost of changes by having
multiple short development cycles ,rather than one long one.
3.Coding:
4.Testing:
Communication : The goal is to give all developers a shared view of
the system which matches the view held by the customer.
Knowledge Transfer: Sharing knowledge about the software with the team.
Test driven development: Negative tests are written even before the code is
coded.
1.Eliminating Waste
2.Amplifying Learning
3.Deciding as Late as Possible
4.Delivering as Fast as Possible
5.Empowering the Team
6.Building Integrity In
7.Seeing the Whole
1.Scrum Roles.
2.Scrum Artefacts.
3.The Sprint Meetings.
4.Scrum Framework Complete Picture.
5.Starting Scrum.
1.Scrum Roles
1.Managing the Stakeholders.
2.Gathering the requirements.
3.Managing and prioritizing the Product Backlog.
4.Working on a shared vision.
5.Managing the release plan.
6.Accepting or rejecting the software at the end of each
iteration.
7.Helps to define the meaning of Done.
1.Process Facilitator .
2.Managing Impediment Backlog.
3.Empowering and shepherding the team.
4.Helps to create information radiators.
5.Helps in building self organizing team.
Self-organising
teams.
2.Scrum Artefacts
Items Size
1.Software Development Methodology Agile Presentation 18
2.Gmat Preparation 20
3.Login Functionality for Loans 12
4.Submitting an application for loan 10
5.Web service call to 3rd party to retrieve info 14
6.Processing the loan 18
7.Booking the loan 15
8.Sending generated documents to user. 14
Task Board / Sprint Backlog
P hy s ica l re p re s e nt a t io n o f t he lis t o f wo rk t he y ha v e c o m m it t e d to
Do d uring t he curre nt s p rint.
Sprint Burndown Chart
1.Sprint 1 will contain 50 story points and 14 days for previous Sprint
backlog.
2.Teams use the sprint Burndown chart to track the product development
effort remaining in a sprint and to monitor its progress.
3.X axis to display working days , Y axis to display remaining effort.
4.It will be a leading indicator of whether it will meet its commitment at the
end of the sprint or not.
1.A Product-Burndown-Chart depicts story points of all user stories in the
so called product backlog.
2.The chart displays story points for each completed sprint, so it
depicts the completion of requirements over time.
3.Backlog and Product-Burndown-Chart is usually updated at the end
of each sprint.
4.New user stories can be added and/or removed before each sprint
planning meeting.
5.Used to show the team and stakeholders how many sprints will be
needed to implement all remaining user stories or how many user
stories can be completed in the remaining time.
Impediment Backlog
8. My re c o m m e nd a t io n to m o s t te a m s is to d o commitment-based
planning.
2.The way in which the Scrum team is working together, including their technical
skills and the software development practices and tools they are using.
3.The sprint retrospective is restricted to the members of the Scrum team that is the
Product Owner, development team members and ScrumMaster.
4.Purpose is to inspect at a deep level how the team is collaborating and performing and
to take action to improve.
5.This often requires deep introspection and sharing, which in turn requires a safe and
secure environment.
4.Scrum Framework
5.Starting Scrum