8/16/2013

Group A-Team
Anton .N.T Lungameni 201051885
Johanes Amwele 213051389
Ester Ndatomwiyo 213028565
Omagano Uushona 213047160

Lecturer: M. Onwordi
Department of Software Engineering
ISW 120s
Assignment 1
Polytechnic of Namibia: I.T. Department
Contents
Question 1 ............................................................................................................................................... 2
a) ......................................................................................................................................................... 2
b) ......................................................................................................................................................... 3
c).......................................................................................................................................................... 3
Question 2 ............................................................................................................................................... 3
a) ......................................................................................................................................................... 3
b) ......................................................................................................................................................... 5
Question 3 ............................................................................................................................................... 5
Bibliography ............................................................................................................................................ 6

ISW Assignment
Question 1

a)

Task Duration (Weeks) Predecessor
1 9w
2 1w 1 (M1)
3 0w 2 (M2)
4 5w
5 2w 2,4 (M3)
6 9w 2,5 (M4)
7 0w 1 (M5)
8 0w 6 (M6)
9 2w 5 (M7)
10 0w 9 (M8)
11 8w 10 (M9)


b)

ES = Earliest start time EF = Earliest finish time Slack = Slack time D = Duration
LS = Latest finish time LF = Latest finish time T = Task
c)

The critical path for this project is:
TASK 1 TASK 2 TASK 5 TASK 9 TASK 10 TASK 11
Question 2

a)
Scrum is a framework for developing complex products, employing various processes and
techniques. It produces products of the highest possible quality.
Scrum consists of the scrum team, events and artifacts. The rules in scrum ensure that they interact
efficiently with each other to have a successful scrum. Scrum uses the empirical process control
theory, which states that knowledge comes from experience and making decisions based on what is
known. Scrum also employs an iterative and incremental approach to improve control risk and
predictability.
Transparency, inspection and adaptation are key in every implementation of empiricism, significant
aspects of the process must visible to the people held accountable for the outcome. Scrum users
must inspect the artifacts and progress frequently during the sprint so avoid undesirable variances.
The scrum user should also adapt when aspects of the process deviate out of the acceptable
constraints, these adaptation must be made as soon as possible.
Scrum Team
- The Product owner
The product owner is responsible for maximizing the value of the product and the work of
the development team. The product owner remains accountable for the Product backlog.
- The Development Team
The development team consists of professionals who will deliver the increment at the end of
each sprint. The development team only acts upon the instructions and requirements set by
the Product owner in the product backlog but nobody tells the team how to turn these into
deliverable increments. Accountability remains with the whole development team and not
individual team members.
- Scrum Master
The scrum master is responsible for ensuring the Scrum and its components are fully
understood and followed by the Scrum team. The scrum master can assist the product
owner in finding techniques in effective product backlog management and facilitate scrum
events. The scum master helps the development team by coaching them in self-organization
and cross functionality, helping create high value products, and removing any obstructions
that will hinder the development process.
Events
- The Sprint
The sprint is a period of about a month where a done, usable product increment is created.
During the sprint no changes are made that would endanger the sprint goal, quality goals
never decrease, and the scope may be clarified and re-negotiated between the product
owner and the development team as more is learned. Only the product owner has the right
to cancel a sprint before it reaches its end.
- Sprint Planning
The sprint planning takes about eight hours and this is where the work to be performed in
the sprint is planned by the whole scrum team. Here the sprint goal is defined.
- Daily Scrum
The daily scrum is a 15 minute meeting held every 24 hours attended by the development
team where they discuss the activities and create a plan for the next 24 hours. They achieve
this by inspecting what work was done in the previous 24 hours and then forecast the work
for the next.
- Sprint review
This an informal meeting that lasts about 4 hours held at the end of the sprint to inspect the
finished increment, it is attended by the scum team and the stakeholders.
- Sprint Retrospective
The sprint retrospective is a meeting where the scrum team inspects itself and plan for
improvements in the next sprint. This meeting occurs between the sprint review and the
sprint planning and lasts for about 3 hours.
Scrum artifacts
- Product backlog
This a list of all features, functions, requirements, enhancements and fixes needed in the
product and is the source for requirements for any changes to be made by the product
owner.
- Sprint backlog
There are no sources in the current document.This is a list of product backlog items
selected for the sprint and a plan for delivering the product increment, this list is compiled
by the development team.

- Increment
The increment is a sum of all the product backlog items completed during a sprint.


b)
Scrum is better suited for a large complex project where change is anticipated and risk of failure is
high, the waterfall process model does not allow for change hence making it inflexible. If something
in the project is changed in the waterfall model the whole process has to be restarted while in the
scrum it will only the sprint for the product increment will be changed. The waterfall model is also
not very transparent, it is difficult to track progress while with the scrum process model the progress
is tracked with daily scrum meetings and sprint evaluation.




Question 3

Component B can use the throw away prototype process model because the clients do not fully
know the requirements and will need our help to fully define them. This process model is best used
for components of large systems. A series of prototypes are first created and presented to the user,
for each prototype, improvements and changes can be made to the requirements and another
prototype is created and validated and presented to the user. This loop is done till a final version is
created.
Component A and C can be integrated using a component based software engineering (CBSE)
because they are both existing commercial off the shelf software. After completing component B the
requirements for the integration of components A and C are fully specified. A component analysis
does not have to be done since through preliminary research they were already identified so we
would move on to modifying the current requirements to reflect the two components, A and C. The
components are then designed and finally integrated and validated.
The final stage is to use incremental process model to complete the information system. The
requirements for the information system can now be defined and the system is broken down into
increments, with the first increments cater for the most critical services of the system so that the
users of the information system can utilize it immediately. The system architecture is then designed
and the development, validation, integration and system validation for each increment can begin.
The most important services will get the most testing when system validation is done for each
increment which will reduce software failures in critical services. The risk of project failure is lower in
the incremental process model.
Bibliography

Headon, T. (2000). Critical Path Methods (C.P.M).
Schwaber, K., & Sutherland, J. (2003). The Scrum Guide.
Sommerville, I. (2007). Software Engineering. Essex: Addison-Wesley.
Wilson, C. D. (2009). A Brief Introduction tto Scrum. Matincor, Inc.



-