As a project manager, you should always think of the schedule as the heartbeat of your project. One of your top responsibilities is to keep your project\u2019s rhythm at a regular pace. It\u2019s like running a race. If you want to succeed, you need to find the right balance and avoid going too fast or too slow.<\/p>\n
To make that happen in projects that have a lot of repetition (hospitals, roadwork, apartment blocks), you have to break down your programme into smaller manageable tasks.<\/p>\n
Like that, you will be able to plan your next steps with precision, maintain better control over your project and prevent delays before they expand out of proportion. If you plan your tasks in days, then any delay that might appear will most probably also result in a delay of a few days. If you make your schedule estimation in months, however, the delays you will have to face will also be in months.<\/p>\n
Bigger chunks of tasks can have a negative impact on your project\u2019s heartbeat and result in outstretched delays. So instead of trying to plan ahead for the entire project from start to finish, it is better to roll out 3-6 week lookahead programmes and link them to the master schedule. In that way, you will have more flexibility when defining the next milestones and you will be able to align your teams around them much easier.<\/p>\n
But here comes the real challenge. Many project managers quickly find themselves lost in a sea of disconnected data because they are using the wrong tools to connect their different schedules.<\/p>\n
They have their master schedule lying around on paper form, detailed programmes stuck in MS Project, numerous updates from the site on WhatsApp and Messenger, outdated reports on Excel, and document approvals lost on email threads. And don\u2019t even mention the endless phone calls and the information that is lost there.<\/p>\n
However, it\u2019s not project managers to blame for this chaotic situation. Working on all these applications makes it impossible to keep track of what\u2019s happening on the field. This is why you need to move all data and project communication to the cloud like you might have already done with your documents.<\/p>\n
If you connect your teams around a live, centralised version of the programme, you will also connect your data and your workflows. This is how Raul Hernandez from Grupo Provivienda<\/a> managed to cut the building time for a house down from 310 to 60 days.<\/p>\n If you also want to learn how you can keep the pulse of your project steady so that you can deliver faster and cheaper like Raul, download our free ebook here<\/a>.<\/p>\n The post Why planning is the heartbeat of your repetitive project<\/a> appeared first on LetsBuild<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"\n
\u201cThe thing that changed was connecting the teams through a live programme that helped us avoid downtime between activities. If your programme is not updated frequently, problems on site get worse because they have not been communicated to the right person quickly,\u201d says Raul.<\/h3>\n<\/blockquote>\n