Agile and CBPM

The question comes up: is CBPM Agile?

The answer is a definite yes. It follows the directions of the Agile Manifesto. It values rolling plans over crafted plans. It is based on regular interactions with project team members and stakeholders. It’s focus is on delivering (“working software” if it’s a software project).

It does not require a cycle such as Scrum, though. In that sense, it’s closer to Kanban, another agile method.

Key points of CBPM:
1. Develop the plan together
2. Make it a rolling plan. In other words, don’t over plan as things may change. Plan just enough to move forward, inspect results, adjust, and lengthen plan.
3. The persons doing the work are the only ones who can commit to a deliverable date.
4. The recipient or customer of the work is the one who says whether it meets expectations. In other words, agree up front on the expectations.
5. CBPM is agnostic with respect to product development methodology. In other words, it can be used for software, hardware, construction, medical devices, etc. Domain-agnostic! Much harder in software-based agile methods.