Agile Pulse Model – Synchronisation plan

The purpose of a synchronisation plan is to divide the project’s product goals into subresults, show in which order the subresults are to be produced in an overall plan for the whole project, organise the work by finding limiting and connected subresults that can be arranged in work packages, identify which team will work with what work package and plan handover points between the work packages. Each work packages should have as few dependencies to other work packages as possible in order to be able to work with them individually.

Results from the Synchronisation plan workshops

An overall plan with fixed points for when each work package should be delivered.

How results are to be generated

Work method. Workshop with those who will work in the project or do work on behalf of the project. Use the nominal group technique.

Premises and material. Workshop room. Whiteboard and pens/markers.

Workshop 1 – The network plan

Step 1.1.

Synchronization plan step 1.1 - Agile Pulse Model
Synchronization plan step 1.1 – Agile Pulse Model


Write two post-it notes – START and FINISHED. Position the notes at each end of the whiteboard.

Step 1.2.

Identify the subresults .

  • What subresults must be generated in order for product goals to be fulfilled?
  • What are the most important steps along the way?

Affix the post-it notes on the board. Remove any doubles.

Step 1.3.

Synchronization plan step 1.3 - Agile Pulse Model
Synchronization plan step 1.3 – Agile Pulse Model


Arrange the subresults in work lines. Identify which subresults are dependent on each other and which subresults are independent. Those that are interdependent are arranged in sequence. Those that are independent are arranged in parallel. Rearrange the post-it notes until there is a logical workflow. Add any subresults that are missing. Draw the interdependencies as lines with a board marker.

Step 1.4.

Number the subresults with a sequence number – 1, 2, 3, etc. Write the sequence number at the top right corner. For each subresult, indicate which other subresults precede it at the bottom left corner.

Step 1.5.


Estimate work time for each subresult. How much efficient work
time is needed to complete each subresult?

Some subresults also contain time for waiting; for example waiting for delivery of materials. In that case, how much calendar time in weeks or days is needed?

Enter work time and duration at the bottom right.


Workshop 2 – Work packages

Step 2.1.

Identify and delimit subresults that belong together and strive for as few dependencies as possible between the work packages. Draw the delimitations in the network plan.

Synchronization plan step 2.2 - Agile Pulse Model
Synchronization plan step 2.2 – Agile Pulse Model


Give each work package a name. Define which subresults each work package is to deliver.

Step 2.2.

Estimate need for resources in each work package based on the work time estimated in the network plan and the skills required. Set resources as R (will work full time in the project), otherwise S as supplier (work part time in several projects).

Each work package is linked to a team. One team can have several work packages.

Workshop 3 – Handover points

Step 3.1.

Synchronization plan step 3.1 - Agile Pulse Model
Synchronization plan step 3.1 – Agile Pulse Model


Identify all handover points between the work packages. Give all handover points an identity in the form of a sequence number.

Step 3.2.

Define at what point in time handover should occur. Protect the handover with a buffer by defining a target time point when you should be finished and a time point when the next team will start.

Step 3.3.

Define definition of done for all handover points. Definition of done describes the results to be delivered at the handover point as well as test and verifications that should be used to secure that the correct results are achieved.

Step 3.4.

Calculate ”speed” for the project. Speed is a measure of how many people on average is working in the project. A low value of speed indicates that there is a lot of sequential work or a lot of waiting
time. A high value of speed indicates that there is a lot of work in parallel due to several teams working in parallel and several people working in each team. A high value on speed is good because that
will reduce the lead time of the project.

Speed = Total work time / (Working hours per week * Number of weeks)

Total work time is picked from the Network plan. Working hours per week are set to 32 hours for one person, which equals 80 % of full time. Number of weeks is the calendar time from the first handover point at the start of the project to the last handover point when the project is complete.

Visually represent the results

By adding the handover points in to the same picture as the network plan and the work packages, you get a compilation of the overall planning. Draw the synchronisation plan in PowerPoint. The name of each work package, and resources needed in each team is documented in Word.

Synchronization plan step 3.5 - Agile Pulse Model
Synchronization plan step 3.5 – Agile Pulse Model


Go from here

Next step, use the synchronization plan to do the first Activity plan triggered at Project pulse.

Back to Agile Pulse Model.

Creative Commons License
Agile Pulse Model by Parmatur HB is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.

Share on Google+0Share on Facebook0Share on LinkedIn0Pin on Pinterest0Share on Reddit0Tweet about this on TwitterPrint this pageEmail this to someone