TeamPort Video Guides
Model Building Steps - a walk through of a first project model and simulation
-
Steps 1 to 4
-
Steps 5 to 8
-
Steps 9 to 12
<
>
|
Start here! Begin a project model with a product, phase, team and 2 activities.
|
|
Learn how to create hierarchy amongst products, teams, and phases known as breakdown structures: PBS, WBS, and OBS
|
|
Learn how to add activities which represent scope towards the realization of products.
|
|
Learn how to allocate teams to activities through contracts, which represent various roles a team can play on an activity, such as primary, decision, quality, and assist roles (PDQA)
|
|
Learn now to add dependencies between activities. Dependence captures a need for something in an activity from another; a demand to interact. Sequence, such as finish to start, is one type of result of dependence, but not the only. Dependence also drives communication and propagating rework.
|
|
Join in a challenge to re-arrange the visual layout and interpret a mystery project. Learn how visualizing a project helps to build mental models and improves ease of conveying what is essential about a project.
|
|
Further refine and expand your project model, and prepare it for simulation.
|
|
Given a project model, generate your first project forecast and plan using a simulator.
|
|
Let's take a look at another project which has some forecasts already generated. What can comparing forecasts tell us about the project?
|
|
Digging into the forecast, can we find insights about expected performance of teams? Which teams are waiting? Why?
|
|
Now that that we have insights from previous forecasts, let's try to make targeted changes to the project and test if they will improve performance.
|
|
As we wrap up these introductory videos, one last step is to share Design Walk, a third application in the TeamPort platform. The Design Walk app shows and compares the set of project models and forecasts, including a tradespace chart.
|