4 Effective Agile Project Management Strategies for Non-IT Projects 

Agile Project Managment

In a construction project this is known as early works and represents parts of the project scope that we can advance ahead of the final product. This could be removing trees in the way of a rail corridor or delivering one equipment set to a military platform ahead of the full project scope. Advantages are that we start to deliver benefits to the end user earlier or reduce the risk for when the final product is released. 

Where you have a long or complicated task that can’t be fully defined upfront, we can utilise the concept of scrums whereby a set of the requirements are worked on first.

These could be the proverbial low hanging fruit that are required before we get to the more difficult items. An example could be a complicated set of documents with multiple parties working to complete them that is estimated to take many months.

We can section the document or task and then assign points for each section which equate to effort. With a rough estimate of these points, we break the planned delivery of months into weeks with several points per week.

We then drive the team to deliver a certain number of points per week with the advantage that we don’t need to rely on a Gantt chart to tell us how we are going on a task such as this a Gantt may only tell us everything is being done in parallel.

Another advantage is that we avoid the mythical man month where a task takes as long as there is time available.

Agile Project Managment

This practice revolves around deferring detailed requirement development until the latest possible time to minimise rework when the full requirement set is known. For instance, in developing a radically new product, the business team might struggle to envision the final product’s functionality. In such cases, providing the cheapest, smallest piece of value—such as site visits, demonstration equipment, trial sites, or prototypes—allows the team to comprehend the product gradually.

While we all appreciate detailed, linked, and resourced schedules, extremely detailed level 5-7 Gantt charts can become unwieldy and no longer reflective of reality. Opting for a job board displaying tasks and their statuses can prove more effective, offering a quick overview of task progress and identifying any blockers.

This approach avoids the complexity of creating intricate logic links in tasks, especially when detailed predecessors and successors are challenging to define.



We welcome you to get in contact should you like to investigate additional ways agile project management can be integrated into non-IT projects, and follow along on LinkedIn.

  

Similar Posts

Remote Work and Mental Health
Remote Work and Mental Health
The challenges and opportunities related to mental wellbeing for people who work remotely have become increasingly relevant. It is not just important,…