Scrum methodology
Agile Methodologies
Before discussing the Scrum methodology, recall the Agile methodology introduced in 126ITSC previously.
The agile approach is an example where planning is incremental and it is easier to change the process to reflect changing customer requirements.
Methodologies within the agile approach share much of the same philosophy, as well as many of the same characteristics and practices.
But from an implementation standpoint, each has its own recipe of practices, terminology, and tactics.
Scrum methodology
• Definition of Scrum
• Why this is used – advantages and Disadvantages
• In the scope of CompSci/Cyber projects
Learning Activity 1
• Learners to:
– Work in your groups to research the Scrum methodology, noting down the purpose of the approach, and outlining what happens in each sprint activity (60 minutes).
– Discuss and write down through your collaborative platform how each phase in the Scrum methodology fits into the scope of computing or cyber security projects (30 minutes).
• Tutor to:
– Provide one-to-one guidance and support to learners.
Tasks and activities in the Scrum process
Scrum is a lightweight framework with broad applicability for managing and controlling iterative and incremental projects of all types.
There are three key roles in SCRUM:
Product Owner: The product owner is the stakeholder and voice of the client.
They are responsible for producing a valuable product and writing customer-centric items for the project backlog.
Development Team: The development team are responsible for delivering a working product (A Potentially Shippable Increment (PSI)) at the end of each sprint cycle. The team is usually between three and nine members who carry out the analysis, planning, development, testing, etcetera on the project.
Scrum Master: The scrum master is in charge of ensuring the project is progressing following the Scrum rules and that the development team can complete a sprint quickly without impediment from external influences.
One of the key aspects of SCRUM is the sprint development iterations. A sprint is a basic development iteration and is often has a fixed length varying between one week and a month.
Sprints begin with a planning meeting where the tasks are identified and an estimation of the commitment to that sprint is made.
Sprints end with a review and retrospective meeting where the progress made is reviewed and any possible lessons from the sprint are documents for later sprints.
Learning Activity 2
• Learners to:
– Work in your groups to discuss how the sprint cycles in the Scrum methodology can be applied to your project. Note down and justify how each activities in the sprints does/doesn’t meet your specific project and scope (90 minutes).
• Tutor to:
– Provide one-to-one guidance and support to learners.