This document is
intended for our project development describing the aspects needed for reviewing
our document/software. The document is planned for review purposes, and assists
as a summary document of the work expected from our group. Software/documents
e.g. source code, project design or requirements should be reviewed every day. When
evaluating, you are mostly aiming to save implementation time, by removing
problems in advance before implementing further.
In order to develop
a strong software quality, reviews are useful in development and knowledge
transfer e.g. code. Software/document review is about finding bugs/styling issues
and typically a good way to make sure the work provided is appropriately
is such a significant moment in a project; a chance to create goals and purpose
to complete the work. Our first meeting would have started with a Kick-off
meeting when for starting on a new project. The main purpose of a kick-off meeting
is essentially to introduce the group and also get an understanding of the
project, understand what needs to be done and then agree on how to work
together effectively. In this way, as a group we are able to be on the same
page. A good kick-off gives a good future result as this displays proper
preparation within the group. This includes assigning each group member a
specific role, what we are doing, how we are going to work together etc.
How we are going to review documents/software and check and indicate
that reviews have taken place.
– Daily Scrum
In creating a sustained
meeting plan, we will be using daily scrum routine to check and indicate that
reviews for documents/software have taken place. Scrum is the most frequently
used in agile work used mostly in software development teams. It is the most
operative way of keeping work in the right path and to make sure product
constraints are met.
In using the
Scrum Structure, we aim to create sufficient meeting times which are vital, making
sure meetings are held every day; this is called the Daily Scrum. During these
meetings sessions, each group member is able to state, what he/she did
yesterday, what will he/she do today and whether there are issues or weaknesses
that 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/she
will say if they had got it done. These sessions are known as ‘Sprints’ which
are fixed to a specific duration, which all future sprint sessions being the
same time duration.
planning in a work place decides how to implement each of the items on their
Sprint Backlog. Each member of the team picks a task from the list. This is very
efficient in making sure reviews have taken place and ensuring sprints (tasks) are
completed. An example of a Sprint Backlog is shown below (Figure 1.1). Using
Sprint Backlog to record our development we are able to deliver more frequent
feedback and allows chances for improvements. Benefits of using Scrum for reviews
is assisting us in helping us to increase the focus within the group for
reviewing software/documents. It is more manageable when tasks are split into
Sprints, this allows us individually in the group to give attention to our
assigned tasks which will help get the work done faster.
Backlog is updated each time: completed tasks are moved to ‘done’, etc. It can
be kept electronically within Excel or with cards on a task board.