Working in an Agile Environment

There are many benefits of working in an Agile environment however, it is often impossible to use “pure Agile” for a variety of reasons. There are cases where specifications might have already been implemented so iterative design simply does not fit the project. To counter this issue, most software development projects will use some combination of Agile and Waterfall. Even in these cases however, a client can still reap the many benefits from working in an Agile environment.

Many software development companies declare they use Agile. This declaration most often applies to the development process only. However, at SSP Software we also use Agile as a customer relationship model. How does this work?

Evaluating the Project

SSP Software specialists perform a cost estimation by examining the task or specifications provided by the client. In the cases where some level of design has already been done, the cost is broken down by tasks or application features. In doing this, the client is able to manage his project budget even before the development starts.

Developing Software

  1. SSP Software managers create a backlog—a list of tasks or features (called user stories). Each of these has its own assessment stated in hours or abstract story points. This method helps inform the client on which features are easy to realize, and which ones will be more difficult.
  2. The project is performed by a defined team of permanent staff.
  3. The development team works according to short (1–2 weeks) iterations with a planning session at the beginning, and a demo session at the end of each one.
  4. The development process is planned in such a way to provide you with visible results after each iteration. This means that after each demo session, we update the application so that you can easily explore any new features and test them.
  5. You always have access to the task board so that you can track the project’s progress, as well as see what other aspects the developers are working on and which tasks are pending.

Accepting Results

  1. You can take part in planning sessions and decide which tasks or features are to be focused on in the next iteration.
  2. You can also take part in the demo sessions and decide which tasks are 100% complete and which ones you think need more work.

Managing Changes

Based on the intermediate results, you can change your requirements at any time and set the process on the right course. The exact way this works depends on which engagement model you choose however, you can be rest assured that the end result will be exactly what you envisioned.