Nimble Work Management
Kairon - Gen AI Solutions
AKT/ AKC Access
→ Agile Methodology
→ Agile Software Development
→ Agile Program Management
→ Scrum Methodology
→ Kanban Methodology
→ Extreme Programming (XP)
→ Behaviour Driven Development (BDD)
→ Feature Driven Development (FDD)
→ Adaptive Software Development (ASD)
→ Dynamic System Development Method (DSDM)
→ Sustainable Pace
→ Story Mapping
→ Test Driven Development
→ Acceptance Test Driven Development
→ Iterative & Incremental Development
→ Pair Programming
→ Unit Testing
→ Acceptance Testing
→ Agile Planning
→ Refactoring in Agile
→ Burndown Chart
→ Lead Time & Cycle Time
→ Agile Velocity
→ Definition of Done
→ Backlog Refinement
→ User Stories
→ Scaled Agile Frameworks
→ Large Scale Scrum (LeSS)
→ Scrum of Scrums
→ Agile Release Train
→ Is SAFe Agile?
→ SAFe Implementations
→ Enterprise Agility With SAFe
→ What is Project Management Lifecycle?
→ What is a Project Management Office (PMO)?
→ What is Agile Project Management?
→ Importance of Project Management
→ What is a Project Roadmap?
→ What is Resource Management?
→ What is Work Management?
To ensure work represents value to customers, you want to deliver it regularly so you can receive immediate and direct customer feedback. This then allows you to adapt as you build and improve the product you’re creating for them.
Yes, this means that everything you planned can change as customer needs change. That’s why Agile Planning, like agile development, is iterative.
And that’s okay because it’s customer value that you’re after, not executing a plan to develop something the customer no longer needs.
Putting the customer at the center of Agile Planning is directly inspired by the first two principles of the Agile Manifesto:
A key component of Agile Planning is its inherent flexibility to adapt to changes in a working environment.
The challenge of delivering projects in the pandemic is a great example of this. During the pandemic, some people became ill and being located in the same building became impossible. This affected everyone involved in developing and delivering new and changed features.
Rather than second-guessing fixed deterministic timelines, Agile uses actual data and metrics to make realistic and informed decisions.
There are several tools for doing this.
One tool often used are Kanban boards and metrics focused on the flow of work through the process and using those to estimate delivery dates for work at hand and in the pipeline.
The main differences between traditional planning and Agile Planning:
The risk with the waterfall approach of making predictions early, when the least is known about what’s ahead, is that the predictions are wildly inaccurate. The reason is that a change in customer needs means that work that’s already been done in earlier stages needs to be redone too.
The Agile Planning approach is inherently iterative and adaptable. Risk is mitigated with customer feedback throughout the project and with each working feature delivered.
It is worth pointing out that the sheer scale of some projects like those undertaken by NASA will follow a more traditional approach to planning or a hybrid of waterfall and Agile called Spiral planning.
Common pitfalls business face are:
Remember where we came in? Agile Planning sounding like a paradox?
Well, now you know that’s not true.
And you know what you need to know to decide whether it is something for you.
If it is, start with getting some solid training and advice. From Digité, of course.
Signup for updates!
Humanize Work. And be Nimble!