Estimation Configuration - Effort Calculation Logic

Put Simply Statement:
Need to create logic to run the calculations for accurate Estimation

Why it Matters:
Accurate estimates and crafting logic

What’s Needed:

• Backend DBs and Data Tables set up

• order of operations / calculation logic development

High Level Overview ;):

Work Items CONC-I-2248 - Gets all work items for each offering detail through an integration with CC

• Come from Offerings

• Have 2 efforts: Baseline & Accelerated

• Admins can assign the following attributes to each Work Item Estimation Configuration: Effort, Accelerators, Driver(s), Complexity(s), Team

  • Work Items have these assigned to them in Concourse Configuration: Name, Description, L level, Offering, Domains, etc (any I'm missing?)

• Work Item effort is calculated by taking the Accelerated Effort and applying the Driver and Complexity Calculations

Accelerators - super simple, we have an integration where we pull in a list of names, their description, and an ID

• Accelerators reduce the baseline effort by the hours assigned for their savings (done on work item page)

• Come from an integration (LeanIX / Nexus)

• Are able to be toggled on or for the Model (or Offering)

• Have some type of definition potentially (Asset Type, Model Type, AI, etc)

Complexity Matrix CONC-I-2268 - I hate this section, but honestly it's pretty simple lol. Complexity Matrix essentially lets you assign more than 1 level of effort for any Work Item
i.e. Work Item = Make Food for a non-complex Work Item we can just say "10 hours" (1 effort number). BUT if we make that a Complex Work Item we can assign differing levels of Effort for different ways of making the food. Low Complexity = Microwaving 1 hour. Medium Complexity = Oven 2 hours High Complexity = Stove 3 hours Insane Complexity = 5000 hours apply to attend Le Cordon Bleu in Paris, receive a Visa, find an apartment, set up a bank account, etc
i.e. Work Item = Test Cases some of these are easy, some are medium, some are hard, those each take different amounts of effort to complete so even though they're all the same work item (Test Cases) the effort for each of them can be super different. This is the fundamental point of complexity matrix

• Can create "Item Types" which are essentially just categorizations of Work Items i.e. Functional vs Technical vs Strategy

• Can search and add work items to each item type

• Can remove both item types and work items

• Can customize the names and number of complexities for the Model (aka 2 complexities, 3 complexities, etc)

• Each work item will have the effort for each complexity input

• Can select the default "counts" for each Item Type

• Each Item Type will only display 1 time to the end user even if there are multiple work items (do we want to maintain this)

• User inputs multiply each complexity's effort by the input

Drivers CONC-I-2251 - simple as well, these are essentially 1 off calculations to impact the effort of a work item i.e. double it, multiply it by 1.1 or 2, etc

• Can create multiple types of drivers (today these are work item variables and program variables)

  • Program variables are applicable to every work item in the Model's scope

  • Work item variables are applied to individual drivers via the Work Item page in Configuration

• Can choose the end User input options (Dropdown vs Input)

  • N of dropdown options + text for dropdowns

• Can create names, descriptions, and names for each of the dropdown selections

• Can choose the effort multiplier/calculation logic

  • Multiplication, duplication, % increase, # of weeks, etc

• Can choose whether or not the driver is visible to end User or not

Teams CONC-I-2281 - more complex, these are the teams that you build to do the work in the Estimate. They can be comprised of N roles from Associate - Partner, and from AC or Domestic

• Can create N teams for a model (i.e. Dev Team, Testing Team, QA Team, PMO Team, Strategy& Team, etc)

  • Can name the teams and add description

• Can create N team structures

  • Team structures determine roll on and roll off timings (what week team members start and finish working on a project)

• Various ways to impact how many hours the roles should perform per week
  
  

Early ACs:

Effort is calculated through an order of operations based on each individual work item in the Estimate

• Gi