Lecture 2 PDF

Preview

Summary

Download Lecture 2 PDF

Description

LECTURE 2 In agile projects, there are short iterations and focuses on collaboration. The teams should work together. You should produce small increments to be make or respond to changes. In agile, there is a continuous planning for every iteration as compared to traditional projects where planning is done at the beginning. Testing at the end of the project in traditional, in agile you test in every iteration. The idea is to produce artefacts in every iteration for the customer. Project breakdown in Agile Projects are broken down in iteration. Each iteration can be between 2-3 weeks. An iteration duration shouldn’t be extended. At the start of iteration, planning occurs at the start. Then developing[analyse, design, development and testing] takes place in realise release and then review at evaluation stage. Product backlog: all the requirements you need for a project. It develops continuous and being updated as we respond to customer changes by adding new items to the product backlog Iteration : selecting work items or requirement from product log to develop work items. You will need estimate the duration of how long it will take to complete item in iteration. This is expressed in story points. Scrum Processes Scrum is a technique you can use to apply agile methodology. Its an incremental process and iterative. An increment should be shippable in an iteration. Team members review activities to perform needed changes at the daily in an iteration. You can’t start a scrum process if you don’t have product backlog. Product Backlog The product backlog includes the functional and non-functional requirements. It has a priority section for every item in the product backlog. User stories are the way we write functional and nonfunctional requirements. The product backlog gives an overview of the project User story The user story must have some of benefit to the customer i.e the customer can use that feature. The user story should tell what user will use a feature and why. The user story cannot describe a technical aspect of a functionality. Follow the user story template in creating good user stories. The user story focuses on the satisfaction of the customer requirements The product owner is responsible to prioritise product backlog as they are the people interacting with customers and business owners. They communicate user needs to the team. The scrum team are not responsible to prioritise items in product backlog. EPICS These are user stories that needs to be broken down and also don’t follow invest module.

Backlog refinement This is not part of scrum but it is recommended....