Skip to main content

This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.

How Agile works at SilverStripe

What is Agile?

Agile methodologies have grown from software development processes. Agile harnesses iterative cycles in which solutions evolve through collaboration between self-organising cross-functional teams. Its principles are summarised in its seminal declaration, the Agile Manifesto.

Agile focuses on people, communication, usable outputs and continuous learning.

When using Agile, teams incrementally deliver working software in short time-boxed iterations. Activities, including feature prioritisation, coding, and testing, happen in parallel. Each iteration builds upon its predecessor until the project is feature-complete.

Agile vs “Waterfall”

Software projects used to be run using a "waterfall methodology." Strict requirements were written into a document. Descriptions of what the software was supposed to do were written into a different document called a functional specification, and many dead trees later, someone would start to write code. This way of creating software came from the physical engineering disciplines. If you are building a bridge, it's very important to get the design correct the first time around because the costs of changing later down the track are so high—not to mention that people's lives may be at risk!

But there are fundamental differences between building software and building bridges, and with Agile, we now recognise those differences. Especially in the fast-paced digital world, it's critical to allow for emerging business requirements to affect the course of development of software. Agile development tends to be better for web projects because:

  • Agile favours smaller iterations of development.
  • Agile focuses heavily on risk management.
  • Communication with you throughout the project is crucial, while heavy-handed documentation is avoided.
  • We have flexible processes and tools in place to guide our projects to successful completion.

What Agile means at SilverStripe

When we use the term "Agile", we actually refer to various components of how we run projects at SilverStripe. Agile encompasses business analysis, risk management, software development, and quality assurance.

Agile also refers to how we engage with you. Most of our clients have multiple-year engagements that are comprised of multiple projects. Each project may have multiple phases, each of which is based on needs determined at the time, not at the beginning of the engagement.

Using Scrum for Agile projects

Scrum is a framework for Agile project management. Scrum is ideal for situations where it is difficult to plan ahead.

In our experience, Scrum is the best methodology for delivering digital projects, particularly the innovative ones our clients come to us for help with. When outcomes are defined at a high level but detailed requirements have not been locked down, incremental delivery of working software and applications provide high business value quickly. It also helps reduce the risk of the unknown, as we are able to tackle the “low hanging risks” early and test our assumptions and ideas throughout the project.

How we use Scrum to deliver better projects

A key principle of Scrum is its recognition that as new information is discovered projects may need to adapt or change path. These unpredicted challenges cannot be easily addressed in a traditional predictive manner.

Scrum adopts an empirical approach—accepting that the problem cannot be fully understood or defined, focusing instead on maximising the team’s ability to deliver quickly and respond to emerging requirements. Work effort is outlined in ‘sprints’, with milestones and goals associated with each sprint. Typically a sprint is a two week-period, with clear deliverables defined and delivered within that period, based on a priority order of feature sets.


Better team results

At SilverStripe, our Agile Project Managers hold a dual role of managing projects and looking after their team as Scrum Masters. As project managers, they update clients on the progress of their projects, keep track of the budgets, and make sure project risks don’t become issues. As Scrum Masters, they make sure any distractions or impediments are removed from the team’s day so that they can work in the most efficient manner. 

Better project results

Using fixed ‘sprint’ cadences, timeframes and budgets can remain stable throughout your project. The project team work closely together with transparency, so that you can own the backlog of work according to your evolving needs.

It was an excellent project to be on. A completely new way of working for me, with a close-knit team who supported each other. Perhaps what I loved most was establishing that rhythm—it was a great way to match ambition with results. ~ Niels Jonker from the NZ Transport Agency

 Find out how Agile can help in your business

SilverStripe's latest tool for Product Owners

In recognising a need for greater communication, SilverStripe has developed the Agile Mojo Booster to clarify the Agile process. If you're interested in becoming a Product Owner, this guide will fill you in on everything you need to know about the role. From definitions to roles and suggestions, the handbook outlines all of the key information you will need when starting your next Agile project. 


Download the Agile Mojo Booster 

book white2

Common Agile Questions

Does my project have to follow an Agile process?
  • A long time ago at SilverStripe, we didn't use Agile. What we found was that in order to complete projects we were working late into the night, yet features may not have been what the client wanted, and sometimes we'd lose money on projects because we were spending much more time on them than we thought we would need to. After we switched over to Agile, we found we could complete projects with the features clients wanted and our staff could get a better job done in less time. Agile is good for us because it's good for our clients. All our projects today are run using the SilverStripe Agile method. What happens when things go wrong?
  • At SilverStripe, we focus on risk prominently and strictly so that we can avoid or mitigate it as best as possible. Our secure online risk register is viewable by you, the client, at any time. Should something unexpected occur, we rely on open, honest communication with you to determine the impact to the project. We will give you choices (and recommendations) about how to proceed in those instances.
Will Agile projects take longer to complete?
  • Actually, we have found that using Agile decreases project length, whilst ensuring higher quality. You see working software sooner and the quality is increased because the project team will have been working with functioning software for a much longer period of time than would have been possible using non-Agile techniques.
Does it cost more?
  • No. In fact, Agile development it usually costs less because we can more reliably deliver to timelines. Often, we will be able to build additional features for sites because of our efficiency in running projects.
With all this communication you keep mentioning, how much involvement will you need on my end?
  • Communication between us and you is critical, but the amount of involvement on your end is flexible and varies according to the needs of the project at any given time. You can generally expect weekly status updates however you would like them—online, on the phone, or in person. There are also usually working sessions where you can be involved a little or a lot. Talk to us about your needs and we can accommodate them.
Why doesn't everyone use Agile?
  • We believe everyone should. We've been using Agile exclusively since 2006 and we have very happy clients. Non-Agile ways of running projects have been around for decades. That's why they have a lot of inertia behind them. The speed at which the web operates has forced a re-evaluation of those traditional methods, and out of that, Agile was born. We expect Agile development will be significantly adopted throughout the web software world. The Future of Software Development is an excellent article that talks about the history of software development and why the Waterfall methodology is not appropriate for web development.