Web Project Management

SCRUM is a project management methodology for software and web development

We believe it is important to involve the client in the strategy, planning, and execution (e.g. design, layout, programming, etc) of every project. Clients need to own their project.

On top of this, software systems constantly face maintenance requirements and re-factors because the world does not sit still.

For eample:

  • web browsers evolve
  • device platforms change
  • ideas and feature requirements evolve
  • security requirements need to be ahead of the game
  • best practice today may be obsolete tomorrow

How can this be dealt with?

 

 

Compare Waterfall to SCRUM
 

WATERFALL is what most people would be familiar with when asking for a quote - one proposal which makes assumptions and attempts fix price upfront.

The issue is that fixed pricing is at best just an educated guess. 

If and when discoveries which had not been considered are exposed, then variations / rework / requoting is required. In the case where the developer has poorly addressed the features thus inheriting the responsibility for the unknowns, this translates into a loss of quality for the client as they try to recover lost hours of rework.

The result often ends in lower quality, reactivity, and sometimes a burnt experience.

 

SCRUM breaks down larger projects into small iterative time-boxed "sprints". The length of a sprint might be one week or two weeks.

Each sprint is locked down during the build and concludes with a team review to re-prioritise the requests for the next sprint. This continuous improvement approach factors in new or changed requests into the next round without having to rescope. Progress is recorded on an item backlog document.

 

Why is SCRUM more effective?

  • it is honest about what work has been done, what is being done, and what has yet to be done
     
  • it puts the customer (i.e. the product owner) and developer onto the same team. Requests are collaborated on as they are discovered and reprioritised
     
  • it provides a more predictable release cycle and
     
  • it connects the value delivery and progress to costs (usally paid at the conclusion of each sprint)
     
  • the project can pause and continue as desired (i.e. a sprint at a time)

 

The best way to understand the difference between the two is by this diagram:

 

 

Why Choose Us?

Most of our new business clients have been referred to us from happy customers.

Our solutions provide our clients with a peace of mind because we spend the time to understand their business, implement in small steps to deliver value quickly, and protect their systems so they can sleep easy at night.

As a business owner, we also understand that you do not have to be tech savvy to know what you want. We only ask you to talk to us so we can understand your issues and begin to solve them with you.

So contact us today.