Software Process
SliQTools use an Agile Software Development process when developing our own software products. When working on customer projects we can use the customer's software process if desired.
Using a Software Process to complete projects that Satisfy Customers
SliQTools Software Process
SliQTools develops software using the SCRUM methodology. Our process allows us to have repeatable results and to complete software projects to your satisfaction.
What is a Software Process?
A software process is the basic framework or set of rules a company uses when developing software. The rules are developed to include a prescribed set of activities that add value to a software development and increase customer satisfaction in the delivered result.
Our process allows us to undertake software projects in a controlled fashion while still absorbing changing requirements.
For a basic description of different software processes, see Kinds of Software Processes.
The SCRUM Methodology
SCRUM is an agile software development process. The SCRUM process was
invented in the early 1990s and was shaped by experience of how
successful software development teams and projects worked.
SCRUM Overview
SCRUM breaks a software development into a series of iterations or
sprints. Each sprint lasts at
most 30 days. During each sprint, a set of features are incrementally
added to the product under development and a potential release of
software is created.
The requirements for the product to be developed are held in a
product backlog.
At the start of a sprint, a sprint planning meeting is held. During the
meeting, a set of requirements from the backlog are picked for
implementation in the next sprint. The development team decides which
requirements they can commit to developing during the next sprint.
At the end of a sprint, a sprint retrospective meeting is held to discuss
which elements of the process could be improved.
Further sprints are then performed until the product backlog of
requirements is empty.
The lifecycle of a project using SCRUM
SCRUM Roles
SCRUM breaks a software project into a number of iterations and defines a
number of roles. The main roles are:-
ScrumMaster
The ScrumMaster makes sure the development team has the resources it needs
to complete the project and interfaces between the developers and
outside influences. The ScrumMaster makes sure the software development
process is followed.
ProductOwner
The Product Owner respresents the customer. The Product Owner must be
available to answer questions concerning requirements for different
aspects of the product under development in order to prevent delays or
misunderstandings. Ideally the Product Owner should be the actual
customer but another person can be nominated to perform this role if
required.
Team
The team consists of the designers, developers and testers who actually
implement the software product.