INTRODUCTION TO SCRUM Lecture 2b

Transcription

1 INTRODUCTION TO SCRUM Lecture 2b COMPSCI 702 Security for Smart-Devices Muhammad Rizwan Asghar March 07, 2017

2 2 WHAT IS SCRUM? An agile software methodology A team works as a unit to reach a goal Requirements might change during the course of the project Usually, the client might change them In this regard, it will depend on what you discover along the way

3 3 EMPIRICAL APPROACH Your team project involves a challenge You have to investigate something that you might not know in advance The problem cannot be fully understood You have to adapt keep going to deliver within the time frame!

4 TEAM ROLES Product Owner Only one The voice of the customer Is part of the Dev Team but cannot be the Scrum Master Scrum Master Only one A buffer between the team and any distracting elements Dev Team Deliver the product! 4

5 5 PRODUCT OWNER (PO) The PO is an interface between me and the team Reporting to me for updates Reporting back to the team Announce releases and milestone reviews Make sure that the Product Backlog is up-to-date and visible Key feature To put oneself in other s shoes

6 6 SCRUM MASTER (SM) The SM makes sure that scrum is followed and pushes the team to improve Helping the PO to ensure the Backlog is neat! Define when a task is completed Remove any impediment for the team to progress Schedule team meetings The SM is not a project manager No tasks related to people management!

7 7 DEV TEAM Main goal Deliver the product Made up of cross-functional skills Analysis, design, coding and documentation Self-organising!

8 EVENTS Sprints Meetings Sprint planning meetings Daily scrum meetings End Meetings Sprint review-and-retrospective 8

9 SPRINTS The basic unit of development Fixed duration defined at the start of the sprint I suggest to start with 1 week Starts with the planning meeting where the sprint backlog is defined Identify tasks Estimate time commitment At the end of a sprint, the review-and-retro meeting is held Could coincide with the starting of the planning meeting for the next sprint 9

10 10 PLANNING A SPRINT Lead by the SM Define work to be done (as backlog items) Facilitate item assignment to team members Ask each team member to give an estimate of the time to commit for each item All members communicate how much work is likely to be done in the sprint

11 11 SCRUM MEETINGS All members come prepared with updates Meeting starts on time without waiting for missing members Each member reports on What has been done What will be doing until the next meeting Is there an impediment preventing you or the team to deliver the sprint on time

12 12 IMPEDIMENTS The SM is responsible for removing the impediments No detailed discussion during Scrum Meetings The SM and the team members can discuss afterwards

13 BACKLOG ITEMS Any given item that will make the product complete Technical, non-functional, features and bug fixes Backlog items are characterised by Priority set by the PO Resource effort set by the dev team Business values, data needed, risk, etc. discussed by the PO and the dev team Ultimately, the PO has the last word on the item prioritisation 13

14 14 BACKLOG GROOMING Ongoing review process to make sure Backlog items are: Up-to-date Properly prioritised

15 BOOTSTRAPPING First sprint All the team members define the backlog items that they can think of Define how new items will be added, removed and changed The PO starts prioritising the items Items with high priority require more details and can be split into sub-tasks the team has to provide the details or set sub-tasks to investigate them The second sprint will consist of the items on top of the backlog 15

16 SPRINT BACKLOG List of Backlog items to be done for the sprint Items are selected from the top of the Backlog (highest priority) Enough items to fill the sprint do not overcommit Sprint Items are broken down to tasks assigned to team members The SM facilitate the assignments At the end of each day, task progress needs to be updated 16

17 17 CHANGES AND STILL MORE CHANGES The Backlog evolves as new knowledge is gathered, customer requirements change Deal with it The dev team and the PO have to work together to make sure that Backlog items are up-to-date and reflect the current status The world changes, the Backlog is never finished!

18 TEAM ORGANISATION By Friday (March 10), I want the groups formed and each PO to send me an (CC course tutor and the team) with Subject Group 702 For each team member Name UPI address 18

19 19 BASECAMP I will set up an account and invite each team No need to create your own account in advance Basecamp will help me and you following progress of your project and to get organised Update Basecamp with what you are doing!!!

20 GRADING At the end of this project, each group has to share Percentage contribution of individual members List of tasks/activities each member was involved in 20

21 21 ACKNOWLEDGEMENT This presentation is a revised version of the lecture delivered by Giovanni Russello, thanks to him!

22 22 Questions? Thanks for your attention!