Agile Development Life Cycle - Scrum

1. Module2: Agile Development LifeCycle (Scrum) https://www.ifourtechnolab.com/custom-software-development

2. Scrum Process https://www.ifourtechnolab.com/custom-software-development

3. 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://www.ifourtechnolab.com/custom-software-development

4. 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://www.ifourtechnolab.com/custom-software-development

5. 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://www.ifourtechnolab.com/custom-software-development

6. Product Backlog- Excel Format https://www.ifourtechnolab.com/custom-software-development

7. 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://www.ifourtechnolab.com/custom-software-development

8. User Stories • User Story is written for the developer • Expresses the increment of value to customer • Vertical slice through the product. https://www.ifourtechnolab.com/custom-software-development

9. User Stories VerticalSlice User Interface Business Layer Data Layer https://www.ifourtechnolab.com/custom-software-development

10. What is Efficient User Stories? • User Story should fit INVESTacronym https://www.ifourtechnolab.com/custom-software-development

11. 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://www.ifourtechnolab.com/custom-software-development

12. 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 bedone by any team member • e.g. Database changes required to do for a user story. https://www.ifourtechnolab.com/custom-software-development

13. Sprint Backlog – Excel Format https://www.ifourtechnolab.com/custom-software-development

14. 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://www.ifourtechnolab.com/custom-software-development

15. Kanban Board Example https://www.ifourtechnolab.com/custom-software-development

16. 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://www.ifourtechnolab.com/custom-software-development

17. Burn-Down Chart https://www.ifourtechnolab.com/custom-software-development

18. Release Burn-Down Chart • Used to track iteration progress against the release plan in a sprint burn down chart https://www.ifourtechnolab.com/custom-software-development

19. Alternative Release Burn-Down Chart • Whatif, • Requirements are changing frequently in eachsprint? • New requirements added in the currentsprint? • The burndownchartinsuchcasesmaynotprovidethecorrectresult • e.g.The teamwasexpectedto finish40storypointsinasprint but completed only 10 storypoints. • Burndownchartshouldalsoprovidesuchimpedimentideassofor suchcases,usealternativereleaseburndownchart. https://www.ifourtechnolab.com/custom-software-development

20. Alternative Release Burn-Down Chart https://www.ifourtechnolab.com/custom-software-development

21. Acceptance Criteria – SecondaryArtifact • 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://www.ifourtechnolab.com/custom-software-development