Agile – Scrum

-By Phani
 Contents
• SDLC
• Waterfall Vs Agile
• Scrum
• Scrum Frame work
• Scrum Flow
• Advantages of Agile
• Dis advantages of Agile
 SDLC
• The software development life
cycle (SDLC) is a framework defining
tasks performed at each step in the
software development process.
 SDLC Methodologies
• Waterfall Model.
• V-Shaped Model.
• Evolutionary Prototyping Model.
• Spiral Method.
• Iterative processing model.
• Incremental Method.
• Agile development.
 Waterfall Model
• It is called as linear-sequential life cycle
model.
• In a waterfall model, each phase must be
completed before the next phase can begin and
there is no overlapping in the phases.
• Any phase in the development process begins
only if the previous phase is complete.
 Drawbacks in Water Fall
• Once an application is in
the testing stage, it is very difficult to go
back and change something.
• No working software is produced until late
during the life cycle.
• High amounts of risk and uncertainty.
• Not a good model for complex and object-
oriented projects.
 Agile Model
• Agile SDLC model is a combination of iterative
and incremental process models.
• Agile Methods break the product into small
incremental builds. These builds are provided in
iterations.
• Each iteration typically lasts from about one to
three weeks.
• Every iteration involves cross functional teams
working simultaneously on various areas.
 SCRUM
• Scrum is a process to maintain Agile perfectly.
• Scrum is a part of the Agile movement or subset
of Agile.
• It is a lightweight process framework for agile
development, and the most widely-used one.
• It enable organizations to adjust smoothly to
rapidly-changing requirements, and produce a
product that meets evolving business goals.
 Scrum Framework
Roles
•Product owner
•Scrum Master
•Team

Artifacts Ceremonies
•Product backlog •Sprint planning
•Sprint backlog •Sprint review
•Burndown charts •Sprint retrospective
•Daily scrum meeting
 Scrum Roles
– Product Owner
• Possibly a Product Manager or Project Sponsor
• Decides features, release date, prioritization, $$$

– Scrum Master
• Typically a Project Manager or Team Leader
• Responsible for enacting Scrum values and practices
• Remove politics, keeps everyone productive

– Project Team
• 5-10 members; Teams are self-organizing
• Cross-functional: QA, Programmers, UI Designers, etc.
• Membership should change only between sprints
 Scrum Artifacts
• Scrum has remarkably few artefacts
– Product Backlog
– Sprint Backlog
– Burndown Charts
• Can be managed using just an Excel
spreadsheet
– More advanced / complicated tools exist
 Product Backlog
• The requirements

• A list of all desired work on project

• Ideally expressed as a list of user stories

along with "story points", such that each
item has value to users or customers of the
product

• Prioritized by the product owner This is the

product backlog
• Reprioritized at start of each sprint
Sample Product Backlog
 Sprint Backlog
• A subset of Product Backlog Items, which define the
work for a Sprint
• Is created ONLY by Team members
• Each Item has it’s own status
• Should be updated every day
• No more than 300 tasks in the list
• If a task requires more than 16 hours, it should be
broken down
• Team can add or subtract items from the list. Product
Owner is not allowed to do it
 Sample Sprint Backlog
Tasks Mon Tue Wed Thu Fri
Code the user interface 8 4 8
Code the middle tier 16 12 10 4
Test the middle tier 8 16 16 11 8
Write online help 12
Write the Foo class 8 8 8 8 8
Add error logging 8 4
 Burndown Charts
• Depicts the total Sprint Backlog hours remaining
per day
• Shows the estimated amount of time to release
• Ideally should burn down to zero to the end of
the Sprint
• Actually is not a straight line
 Ceremonies
• Sprint Planning Meeting
• Daily Scrum
• Sprint Review Meeting
• Sprint Retrospective
 Sprint
• Sprint is simply a iteration in Agile.
• Sprints are always short: normally about
2-4 weeks.
• Each Sprint begins with the Daily Scrum
Meeting.
Sprint Planning
 Parts of Sprint Plan Meeting
• 1st Part:
– Creating Product Backlog
– Determining the Sprint Goal.
– Participants: Product Owner, Scrum Master,
Scrum Team
• 2nd Part:
– Participants: Scrum Master, Scrum Team
– Creating Sprint Backlog
 Daily Scrum Meeting
• Parameters
– Daily
– 15-minutes
– Stand-up
– Not for problem solving
• Three questions:
1. What did you do yesterday
2. What will you do today?
3. What obstacles are in your way?
• Chickens and pigs are invited
– Help avoid other unnecessary meetings
• Only pigs can talk
 “Pigs” And “Chickens”
• Pig: Team member committed to success of project
• Chicken: Not a pig; interested but not committed

A pig and a chicken are walking down a road. The chicken looks at
the pig and says, "Hey, why don't we open a restaurant?" The pig
looks back at the chicken and says, "Good idea, what do you want
to call it?" The chicken thinks about it and says, "Why don't we call it
'Ham and Eggs'?" "I don't think so," says the pig, "I'd be committed
but you'd only be involved."
 Sprint Review Meeting
• Team presents what it accomplished during the sprint
• Typically takes the form of a demo of new features or
underlying architecture
• Informal
– 2-hour prep time rule
• Participants
– Customers
– Management
– Product Owner
– Other engineers
 Sprint Retrospective Meeting
• Scrum Team only
• Feedback meeting
• Three questions
– Start
– Stop
– Continue
• Don’t skip for the first 5-6 sprints!!!
Scrum Process
 Advantages of Agile - Scrum
• Advantages
– Completely developed and tested features in short
iterations
– Simplicity of the process
– Clearly defined rules
– Increasing productivity
– Self-organizing
– Each team member carries a lot of responsibility
– Improved communication
– Combination with Extreme Programming
Drawbacks Of Agile - Scrum
- “Undisciplined hacking” (no written
documentation)
- Violation of responsibility
- Scrum isn’t as easy as it looks -
Be ready to invest time and effort to get good at
Scrum
- Scrum can make some people very
uncomfortable
- Usage of Limited resources
Than Q
By Phani