There are many articles about Agile, but this one is about describing it in my own words, how I’ve come to understand it and my own experience with it.
What is Agile?
Agile is a philosophy and methodology. It is a way of working, in which a team of individuals from various disciplines come together to deliver a project – be it a new digital service, feature or product.
The Agile Manifesto, was written 17 years ago in 2001 by a group of software developers and describes Agile as “…uncovering better ways of developing software by doing it and helping others do it.”
The Agile values and Sprint 0
A summary of the agile values:
- Individuals and interactions over processes and tools
- Working software over comprehensive documentation
- Customer collaboration over contract negotiation
- Responding to change over following a plan (Beck et al, 2001)
Agile is great way to break a project down into manageable parts, for example, the minimal viable product with its subsequent releases.
But before a project even starts it can be helpful to do some planning. The time before kicking off your project is sometimes referred to as sprint 0.
Using the pitch document as a north star for your project
It can be helpful to compile a positioning document (sometimes referred to as a pitch deck) for a project during the planning phase. This is a document that guides you, your team and other stakeholders on a mission and vision for your project. While you may pivot during your project, this document will ensure that you don’t veer off-course too dramatically.
Conduct concept testing
Before starting a project it may also be a good idea to test your concept with staff and customers to find out if it will be a viable solution for the segment that you are targeting. Include the findings of your research in your positioning document.
The importance of technical viability
While some of us may want to live on Mars, the idea may not yet be technically or financially feasible. A positioning document should include how your solution will be implemented technically and should:
- Elaborate on the financial benefit as well as the customer benefit that your product, feature or service offering might land.
- Include a high level view of the financial benefits like a potential savings, increased profits or decrease in customer attrition.
- Cover what your competitors are doing: a snapshot view of what innovation is out there in the market already.
Innovation is not about copying a competitor but about coming up with something new or different, aligned to your organisation’s values. Companies often offer competitive services, features or products (think of the travel industry). But because every organisation has its own values, culture and customer base, each should differentiate to offer a unique value proposition. In summary, context is everything.
Planning releases
Your positioning document should break your project up into different technical and commercial releases. A great timeline to work towards is 6 – 10 sprints per release. A sprint is usually 2 weeks long and is planned around Agile rituals like Show & Tell, Retrospective and Sprint Planning.
Once you’ve proved the viability of your idea (that customers want it, that is it technically feasible and commercially viable) you can kick off your project. Keep your positioning document handy. Ready, set, go!
Agile projects delivered
- Digital channel access for small business owners
- Digital onboarding for small business products
- Financial tracking tool for digital channel users
Read about the importance of client centricity in delivering Agile products.
