Sample donated: Archie Copeland
Last updated: February 14, 2019
Introduction This document isintended for our project development describing the aspects needed for reviewingour document/software. The document is planned for review purposes, and assistsas a summary document of the work expected from our group. Software/documentse.g.
source code, project design or requirements should be reviewed every day. Whenevaluating, you are mostly aiming to save implementation time, by removingproblems in advance before implementing further. In order to developa strong software quality, reviews are useful in development and knowledgetransfer e.g. code.
Software/document review is about finding bugs/styling issuesand typically a good way to make sure the work provided is appropriatelydocumented. 2. Kick-off Meeting Kick-off meetingis such a significant moment in a project; a chance to create goals and purposeto complete the work. Our first meeting would have started with a Kick-offmeeting when for starting on a new project. The main purpose of a kick-off meetingis essentially to introduce the group and also get an understanding of theproject, understand what needs to be done and then agree on how to worktogether effectively.
In this way, as a group we are able to be on the samepage. A good kick-off gives a good future result as this displays properpreparation within the group. This includes assigning each group member aspecific role, what we are doing, how we are going to work together etc. 3. How we are going to review documents/software and check and indicatethat reviews have taken place.- Daily ScrumIn creating a sustainedmeeting plan, we will be using daily scrum routine to check and indicate thatreviews for documents/software have taken place. Scrum is the most frequentlyused in agile work used mostly in software development teams.
It is the mostoperative way of keeping work in the right path and to make sure productconstraints are met. In using theScrum Structure, we aim to create sufficient meeting times which are vital, makingsure meetings are held every day; this is called the Daily Scrum. During thesemeetings sessions, each group member is able to state, what he/she didyesterday, what will he/she do today and whether there are issues or weaknessesthat will need to be worked on. For example, if a member in our group says”Today, I will finish A, B and C”, we will know in tomorrow’s meeting; he/shewill say if they had got it done. These sessions are known as ‘Sprints’ whichare fixed to a specific duration, which all future sprint sessions being thesame time duration. Team sprintplanning in a work place decides how to implement each of the items on theirSprint Backlog. Each member of the team picks a task from the list.
This is veryefficient in making sure reviews have taken place and ensuring sprints (tasks) arecompleted. An example of a Sprint Backlog is shown below (Figure 1.1). UsingSprint Backlog to record our development we are able to deliver more frequentfeedback and allows chances for improvements.
Benefits of using Scrum for reviewsis assisting us in helping us to increase the focus within the group forreviewing software/documents. It is more manageable when tasks are split intoSprints, this allows us individually in the group to give attention to ourassigned tasks which will help get the work done faster. Figure 1.1The SprintBacklog is updated each time: completed tasks are moved to ‘done’, etc. It canbe kept electronically within Excel or with cards on a task board.