Adaptive Life Cycles by PMBOK


Interesting fact.

Agile actually has a global impact on project management standard, especially on PMBOK. Just take last PMBOK edition (5th) and read article 2.4.2.4 about Adaptive Life Cycles. Conclusions is your own deal 🙂

2.4.2.4 Adaptive Life Cycles
Adaptive life cycles (also known as change-driven or agile methods) are intended to respond to high levels of change and ongoing stakeholder involvement. Adaptive methods are also iterative and incremental, but differ in that iterations are very rapid (usually with a duration of 2 to 4 weeks) and are fixed in time and cost. Adaptive projects generally perform several processes in each iteration, although early iterations may concentrate more on planning activities.
The overall scope of the project will be decomposed into a set of requirements and work to be performed,
sometimes referred to as a product backlog. At the beginning of an iteration, the team will work to determine how many of the highest priority items on the backlog list can be delivered within the next iteration. At the end of each iteration, the product should be ready for review by the customer. This does not mean that the customer is required to accept delivery, just that the product should not include unfinished, incomplete, or unusable features.
The sponsor and customer representatives should be continuously engaged with the project to provide feedback on deliverables as they are created and to ensure that the product backlog reflects their current needs.
Adaptive methods are generally preferred when dealing with a rapidly changing environment, when requirements and scope are difficult to define in advance, and when it is possible to define small incremental improvements that will deliver value to stakeholders.

Process – Communications management


Project Communications Management includes the processes that are required to ensure timely and appropriate planning, collection, creation, distribution, storage, retrieval, management, control, monitoring, and the ultimate disposition of project information.

Effective communication creates a bridge between diverse stakeholders who may have different cultural and organizational backgrounds, different levels of expertise, and different perspectives and interests, which impact or have an influence upon the project execution or outcome.

The key benefit of this process is that it identifies and documents the approach to communicate most effectively and efficiently with stakeholders.

Download:


Share and comments are always appreciated!

Process – Scope and Change request management


Scope and change request management is a direct way to meet customer expectations.

So main idea for this process – gather requirements / change requests, discuss them in one place and give clear feedback for each requirement and change request.

 

Download:


Share and comments are always appreciated!

Process – Document flow


Culture of document flow as one of the key figure of the project maturity.

Clear doc flow, single style of documents and templates can significantly increase quality of issued documents.

Finally, your project will get priceless benefit – you make next step to customer satisfaction.

 

Download:


Find something interesting – please, share and leave comments!

Template – Project Scope Statement


All phases.

Template – Project Scope Statement.

So many tools, so many processes, so … and so.

Make access to ALL facets of the project from one place.

It’s your the fastest way to put someone new in the project!

Project Scope Management-3

And of course, there are lots of ways to use it. For example – audit purposes, new team member introduction, TOP-management overview and so on.

Download Project Scope Statement.


Find something interesting – please, share and leave comments!