Modeling projects

Basic guide to modelling projects in A-Dato Lynx.

Projects in Lynx: Sanity checking the project before release

1. Project is configured as just-in-time (JIT):
   1. Project start date is "Use current date" (Properties > Project dates > Project start date).
   2. Project has an end date (Properties > Project Dates > Project end date)
   3. Schedule engine is configured as JIT for both the main chain and feeding chains (Properties > Scheduling > Schedule engine):
      1. Schedule tasks 'just in time' selected.
      2. Activate CCPM schedule engine On.
      3. Schedule feeding chains 'just in time' selected.

   ℹ️ ASAP projects are rare, but there can be legitimate reasons to prefer ASAP scheduling for a project, such as training or onboarding projects.

2. The project is feasible: the start date of the first task is today, or later.
3. There are no completed tasks
4. All tasks have story points
5. If you intend to have all tasks done by a single person (which is how we currently work), assign that person as the resource to every task. If the tasks can be distributed, assign the DevTeam skill on the tasks, so that Lynx can distribute the work.
6. There are no tasks with a duration of [0 days]
7. There are no tasks that run past the deadline, shown as the blue area in the project timeline.
8. CCPM compliance checks (top right checkmark button in the project overview) report no issues, specifically:
   1. A project buffer is part of the plan.
   2. The project network is closed, all tasks lead to a single endpoint.
   3. All tasks have resources and/or skills assigned.
9. Project performance on the overview page is 0% for both values, after releasing

Lynx: Start working on a task

1. Go to tab "Active tasks"
2. Sort by Start Date
3. Click on task to be started
4. In right side panel > click on Resource(s) > Click on checkbox for your name/li>
5. Click OK
6. Change status to Started

After working on this task for a day, before the next Daily:

1. Go to tab "Active tasks"
2. Click on task you started earlier
3. Enter the ettc (Estimated time to complete) based on your work so far

Lynx issues

Assigning resources before assigning story points

Conversion of story points to durations is done when and only when the resources are first assigned. If you create a task, do not set a story point estimate, and assign a resource, Lynx will set the duration to "[0 days]". This value will not update when you enter a new story point estimate.

Avoid this by assigning resources after you add story point estimates. As the only resource we generally use is "DevTeam" this is fairly easy.

Fix this problem by unassigning the resource and reassigning it.