Anyone that's led an IT project understands that there is any number of risks that threaten the delivery timeframe and the project budget.
Sometimes these risks are known, other times they only become apparent when the delivery deadline is looming. Every time an issue presents itself, there's an opportunity to learn and mitigate that issue from happening next time.
That's exactly what the Way of Working: Agile Development Playbook embraces.
Over years of developing software applications for almost every industry, we've encountered our fair share of issues.
Rather than try to use that information as a competitive advantage, we're sharing it with you.
That way you benefit from a process that already knows the risks you're likely to face and mitigates them.
Packed with strategies that helped the Department of Defence win innovation awards.
Agile is a fantastic methodology. These days, it's the industry standard.
What frustrates us is seeing the agile methodology being used as an excuse for poor documentation, missed deadlines and scope creep.
Why?
Because agile still needs structure.
That's where the Way of Working comes in.
This playbook adds structure to the process to ensure that the right stakeholders are involved at the right times, an application is documented and valuable products are delivered within the timeline.
We look at the #1 question every project lead is asking:
While the activities and strategies in the Way of Working are relevant to any ICT professional, we would especially recommend it for the following:
- Project managers looking to improve the velocity and output of their development teams.
- Product owners wanting a process that will deliver a quality application on time and budget.
- CEOs, CIOs and business managers who want a greater understanding of how they can balance agile with organisational necessities.
- Any other stakeholder (designers, software engineers, business analysts, project managers) that is involved in software projects and is looking for new strategies and tactics.
The beginning of any software development project is by far the riskiest time for all involved if not approached from the right angle.
The Cone of Uncertainty (on the right) is a depiction that as we go further into the future there is more that we are uncertain about.
There are so many other factors that may impact a project in 6 months time that we just don’t know about currently.
For example, Apple/Google may update their software requirements or a particular plugin we were planning to use has reached end-of-life.
This is why it’s important to break down the project into smaller builds. Each build can be scoped at the relevant time allowing greater certainty around the estimated length.
$39
These resources have been developed to give every project the best possible chance to succeed.