Agile Development Life Cycle - Scrum
                     Module 2:
Agile Development Life Cycle
(Scrum)
https://wwwhtt.ipfo:/u/rwtewcwhn.ifooluarbt.eccohmno/claubs.tcoom-software-development
Scrum Process
https://wwwhtt.ipfo:/u/rwtewcwhn.ifooluarbt.eccohmno/claubs.tcoom-software-development
Scrum Artifacts
• Primary (Main) Artifacts
• Product backlog
• User Stories
• Product backlog sizing
• Sprint backlog
• Kanban Board (Signboard / Billboard)
• Burn-down chart
• Secondary Artifacts
• Acceptance Criteria.
https://wwwhtt.ipfo:/u/rwtewcwhn.ifooluarbt.eccohmno/claubs.tcoom-software-development
Product Backlog
• List that represents customer’s needs and wants
• Requirements are always defined into user stories in a product backlog
• Managed by product owner
• Product owner can add or remove user stories
https://wwwhtt.ipfo:/u/rwtewcwhn.ifooluarbt.eccohmno/claubs.tcoom-software-development
How To Create Product Backlog?
• Typical product backlog comprises following different types of items:
• Features
They are described in the form of user stories
• Bugs
It is almost same as the feature
• Technical Work
e.g. Upgrade all developer’s work station to windows 10
• Knowledge Acquisition
e.g. Researching about various JavaScript  libraries.
https://wwwhtt.ipfo:/u/rwtewcwhn.ifooluarbt.eccohmno/claubs.tcoom-software-development
Product Backlog- Excel Format
https://wwwhtt.ipfo:/u/rwtewcwhn.ifooluarbt.eccohmno/claubs.tcoom-software-development
Product Backlog- Excel Format
• Product backlog in this manner is written in the form  of user stories
• The form is like “As a, so that…” e.g. As an administrator should be able to inactive 
any registered user so that such user can not login to the system
• The spreadsheet helps to divide each part of the requirements in to specific columns
• You can add columns as per your requirements like Status column.
https://wwwhtt.ipfo:/u/rwtewcwhn.ifooluarbt.eccohmno/claubs.tcoom-software-development
User Stories
• User Story is written for the developer
• Expresses the increment of value to customer
• Vertical slice through the product.
https://wwwhtt.ipfo:/u/rwtewcwhn.ifooluarbt.eccohmno/claubs.tcoom-software-development
User Stories
Vertical Slice
User Interface
Business Layer
Data Layer
https://wwwhtt.ipfo:/u/rwtewcwhn.ifooluarbt.eccohmno/claubs.tcoom-software-development
What is Efficient User Stories?
• User Story should fit INVEST acronym
Independent Should be self contained There should not  be inherent 
dependency on another story
Negotiable Can always be changed and rewritten until  they are 
part of a sprint
Valuable Must deliver value to the customer
Estimable Must always be able to estimate the size of  a user story
Sized Appropriately Should not be so big to plan /  prioritize
Testable Must provide necessary information to  make test driven 
development possible
https://wwwhtt.ipfo:/u/rwtewcwhn.ifooluarbt.eccohmno/claubs.tcoom-software-development
Backlog Sizing
• Estimating anything is a tricky task but comparing  anything is simpler and better
• Sizing a backlog is all about making decision based  upon,
• Complexity
• Amount of work (Efforts estimation)
• It is not about how long it will take to do the work.
https://wwwhtt.ipfo:/u/rwtewcwhn.ifooluarbt.eccohmno/claubs.tcoom-software-development
Sprint Backlog
• Subset of Product Backlog
• Sprint backlog created during sprint planning  meeting
• User stories and tasks to accomplish or remaining to  complete from previous 
sprint
• User stories will be divided into tasks during the  sprint
• Task is a small chunk of a user story that can be done by any team member  
      e.g. Database changes required to do for a user story.
https://wwwhtt.ipfo:/u/rwtewcwhn.ifooluarbt.eccohmno/claubs.tcoom-software-development
Sprint Backlog – Excel Format
https://wwwhtt.ipfo:/u/rwtewcwhn.ifooluarbt.eccohmno/claubs.tcoom-software-development
Kanban Board
• Kanban is a Japanese word of Signboard or Billboard
• Kanban board is a task board
• Visible to entire organization
• Comprises,
• All tasks to be done by team during the sprint will be displayed on task board
• Setup meetings to gather requirements
• Review checks
• Research
• Testing
• Design
• Stages of coding.
https://wwwhtt.ipfo:/u/rwtewcwhn.ifooluarbt.eccohmno/claubs.tcoom-software-development
Kanban Board Example
https://wwwhtt.ipfo:/u/rwtewcwhn.ifooluarbt.eccohmno/claubs.tcoomm-software-development
Burn-Down Chart
• Visual way to track how the sprint is progressing on  daily basis
• Sprint backlog supplies the information for burn down  chart
• Indicates remaining work
• Provides early indication if there is a problem in the  sprint and the team may not 
fulfill the commitment
• Burn down chart is used to analyze during sprint  retrospection meeting about 
how the sprint was  progressed and where it can be improved in the next  sprint.
• There are 2 types of burn down charts,
• Sprint Burn Down Chart
• Release Burn Down Chart.
https://wwwhtt.ipfo:/u/rwtewcwhn.ifooluarbt.eccohmno/claubs.tcoom-software-development
Burn-Down Chart
https://wwwhtt.ipfo:/u/rwtewcwhn.ifooluarbt.eccohmno/claubs.tcoom-software-development
Release Burn-Down Chart
• Used to track iteration progress against the release plan in  a sprint burn down 
chart
https://wwwhtt.ipfo:/u/rwtewcwhn.ifooluarbt.eccohmno/claubs.tcoom-software-development
Alternative Release Burn-Down Chart
• What if,
• Requirements are changing frequently in each sprint?
• New requirements added in the current sprint?
• The burn down chart in such cases may not provide the correct result
• e.g. The team was expected to finish 40 story points in a sprint  but 
completed only 10 story points.
• Burn down chart should also provide such impediment ideas so for  such cases, 
use alternative release burn down chart.
https://wwwhtt.ipfo:/u/rwtewcwhn.ifooluarbt.eccohmno/claubs.tcoom-software-development
Alternative Release Burn-Down Chart
https://wwwhtt.ipfo:/u/rwtewcwhn.ifooluarbt.eccohmno/claubs.tcoom-software-development
Acceptance Criteria – Secondary Artifact
• Set of steps that developer must complete before the story can be considered 
done
• Created by product owner with the help of customer
• Upfront sets the expectation of the user story
• Helps to write automated tests or to implement TDD
https://wwwhtt.ipfo:/u/rwtewcwhn.ifooluarbt.eccohmno/claubs.tcoom-software-development