Back To Basics: Deep Dive Part 12

Analysis that helps the plan

Critical role of analysis in the planning

All the plans change when the first bullet is fired. -Helmuth von Moltke

This speaks volumes. There must be plans: Strategic plans, program planning, detailed plans.But projects must be geared to be able to handle change – cause things do change.

The analyst’s output is fundamental to the planning of a project. It is the source of the project plan.

So why is this a principle?

Analysts play a significant role in this process. What makes a project successful is the part that engages with the customer and the project management team to set the scope, budget, timelines and expectations.

Thus, embedded in the analysis process is the scope, units of work that flow from it and the order in which it must be delivered.

Consider the following aspects that must be achieved by one’s analysis:

1. Analysis good enough for estimates1.

The documented requirement details must not just be enough detail for the developer to know what to do, but also enable the developer to estimate how long it will take.

2. Customer scope expectations

Customers have expectations. Irrespective of the delivery model (agile, waterfall, hybrid), the analyst must manage these expectations.

This can be achieved by the following:

Sign off core scope requirements
Allow for changes in the process, with the customer understanding the impact of them
Align often by reviewing changes and doing showcases / demos

The analyst’s job remains to empower the project manager to plan and execute the plan

You can download the whitepaper from https://jalia.co.za/services/

Author: Henk Maritz (jalia.co.za)

No part of this publication may be copied or used in any form without prior written permission from the author.