Software development methodologies at Springtimesoft Consulting

We’re always on the lookout for new and better ways of doing things and using different processes to deliver things in the best possible way.

To date we have not settled on one single methodology but take pieces from several well known methodologies. Ultimately, each project and client calls for a different approach.

We have learnt that above all else it’s important to have a genuine focus on collaboration and partnership, together with a high level understanding of what all parties are trying to achieve. This includes the short term (business models, validation, prototypes) and long term requirements (mission, saleability, scaling).

Below we have outlined some concepts we draw inspiration from and what we find really valuable about each.

Lean Startup/Customer Driven

Lean startup was born out of the premise that time is precious and finite. Deeply understanding what problems your customers have and how your solution addresses them makes pursuing the right solution much faster and cheaper. We use the Lean Canvas to map business models. We then go through each component of the business model systematically validating each part. Most of this validation is done via interactions with real potential customers.

Prototyping

We build prototypes to gain insight into how a product should be structured technically, as well as trying different modes of interaction between the end user and the product (UX/UI prototyping). Requirements or user stories are often mentioned during the initial prototyping phase and this allows us to learn the “hot paths” of the software and experiment with ideas without sacrificing a production code base. Prototypes are eventually thrown away and the learnings are used to architect more robust production software.

Iterative and Incremental

Tying into the Lean methods mentioned above, having an iterative and incremental approach to development helps to enforce the tight “feedback loop” that is desired in the Lean model (i.e. make small changes and measure the outcomes).

Agile/Scrum

We use Agile and scrum to provide a highly flexible approach to development. It suits projects that have or need:

• Cross functional teams
• High level of collaboration
• Ongoing involvement from all stakeholders
• Flexibility around change

It is change-driven meaning it’s designed to embrace and facilitate change. This means that teams can always be working on what is most important at any given time. Work is done in sprints which have a fixed time and resource. Typical sprint length is 2 - 4 weeks.

Waterfall

This is a more traditional approach that has been the target of criticism around lack of flexibility. We find Waterfall works with small, well defined projects or tasks.

We always strive to deeply understand our clients needs and ensure we’re working on the things that matter to the organisation the most.

If you have feedback or questions on how we work please feel free to get in touch.