Skip to content

Latest commit

 

History

History
353 lines (318 loc) · 15.4 KB

AzureDevOpsProcessTemplateSetup.asciidoc

File metadata and controls

353 lines (318 loc) · 15.4 KB
Raw

Appendix: Azure DevOps Process Template Setup

To setup an Azure DevOps process template that is configured to work with T-Minus-15, navigate to Organisation Settings > Process and then "All processes".

Under "…" for "Agile (Default)" click on "Create inherited process".

  1. Name: T-Minus-15

  2. Description: This process template supports the T-Minus-15 methodology as outlined at https://github.com/BenGWeeks/T-Minus-15

Extensions

Install the following extension:

  1. Personas

  2. [Optional] Harvest Time Tracker

Epic

For the Epic, perform the following steps on the Details page:

  1. Edit the Description field,

    1. Rename the Layout > Label from "Description" to "Objective".

    2. Change Options > Required to True.

  2. Create a new field "Technical Solution", with:

    1. Definition > Name: Technical Solution

    2. Definition > Type: Text (multiple lines)

    3. Definition > Description: Outline what technologies will be used to deliver the solution.

    4. Layout > Label: Technical Solution

    5. Page: Details

    6. Group (new): Technical Solution

    7. Column: Left

  3. Create a new field "Licensing, Permissions and Accounts", with:

    1. Definition > Name: Licensing Accounts

    2. Definition > Type: Text (multiple lines)

    3. Definition > Description: Provide requirements and guidance around licensing (including costs), service accounts and access/permissions needed.

    4. Options> Default value: <i>Outline what licenses and permissions the accounts will need to access the system, as well as licensing and permissions for any accounts that we need to deliver the solution.</i>

    5. Layout > Label: Licensing, Permissions and Accounts

    6. Layout > Group: Licensing, Permissions and Accounts

    7. Layout > Column: Left

  4. Edit the "Effort" field,

  5. Rename the Layout > Label from "Effort" to "Engineering Effort (Days)"

  6. Change the Definition > Description from "The estimated effort to implemented the epic" to "The estimated engineering effort to implemented the epic"

  7. Create a new field "Prep Effort (Days)"

    1. Definition > Name: Prep Effort

    2. Definition > Type: Decimal

    3. Definition > Description: The estimated prep effort to implemented the epic

    4. Layout > Label: Prep Effort (Days)

    5. Layout > Group: Planning

  8. Create a new field "Design Effort (Days)"

    1. Definition > Name: Design Effort

    2. Definition > Type: Decimal

    3. Definition > Description: The estimated design effort to implemented the epic

    4. Layout > Label: Design Effort (Days)

    5. Layout > Group: Planning

  9. Create a new field "Test Effort (Days)"

    1. Definition > Name: Test Effort

    2. Definition > Type: Decimal

    3. Definition > Description: The estimated test effort to implemented the epic

    4. Layout > Label: Test Effort (Days)

    5. Layout > Group: Planning

  10. Create a new field "Planning Effort (Days)"

    1. Definition > Name: Test Effort

    2. Definition > Type: Decimal

    3. Definition > Description: The estimated planning effort to implemented the epic

    4. Layout > Label: Test Effort (Days)

    5. Layout > Group: Planning

  11. Create a new field "Operate Effort (Days)"

    1. Definition > Name: Operate Effort

    2. Definition > Type: Decimal

    3. Definition > Description: The estimated operate effort to implemented the epic

    4. Layout > Label: Operate Effort (Days)

    5. Layout > Group: Planning

  12. Create a new field "Contingency (%)"

    1. Definition > Name: Contingency

    2. Definition > Type: Picklist (integer)

    3. Definition > Description: The contingency varies based on clarity and risk associated with the estimated effort for projects.

    4. Definition > Picklist items: 30, 25, 20, 15, 10, 5, 0 (add in this order)

    5. Layout > Label: Contingency (%)

    6. Layout > Group: Planning

  13. [Optional] Create a PO Status (%)

  14. [Optional] PO Days (excluding contingency and operate)

  15. [Optional] PO Days (including contingency but excluding operate)

  16. [Optional] Order Value (€) (including contingency but excluding operate)

  17. [Optional] Discount Value (€)

  18. Create a new field "Client"

    1. Definition > Name: Client

    2. Definition > Type: Text (single line)

    3. Definition > Description: Provide the client whom we are supplying this solution to.

    4. Layout > Group: Classification

  19. Create a new field "Project Type"

    1. Definition > Name: Project Type

    2. Definition > Type: Picklist (string)

    3. Definition > Description: Specify the type of project.

    4. Definition > Picklist items: Workshop, Tender, Project, MSA, Consultancy

  20. Create a new field "Proposal/MSA Link"

    1. Definition > Name: Proposal or MSA Link

    2. Definition > Type: Text (single line)

    3. Layout > Label: Proposal/MSA Link

    4. Layout > Group: Classification

  21. Create a new field "Scrum Master"

    1. Definition > Name: Scrum Master

    2. Definition > Type: Identity

    3. Definition > Description: Specific who will be the scrum master

    4. Layout > Group: Classification

  22. [Optional] Account Manager

  23. [Optional] Customer Success Manager

  24. Create a new field "Product Owner"

    1. Definition > Name: Product Owner

    2. Definition > Type: Text (single line)

    3. Definition > Description: Specific who will be the product owner

    4. Layout > Label: Product Owner (Email)

    5. Layout > Group: Classification

  25. [Optional] Order Number

  26. [Optional] Strategic Theme

  27. Hide Planning > Priority

  28. Hide Planning > Risk

  29. Hide Planning > Business Value

  30. Hide Planning > Time Criticality

For the Epic, we need to populate a new "Epic Hypothesis" page:

  1. Create a new page called "Epic Hypothesis".

  2. Create a new field "Value Statement"

    1. Definition > Name: Value Statement

    2. Definition > Type: Text (multiple lines)

    3. Definition > Description: Outline the benefits of this Epic

    4. Layout > Label: Value Statement

    5. Layout > Group (new): Value Statement

    6. Layout > Column: Left

  3. Create a new field "Business Outcome Hypothesis"

    1. Definition > Name: Business Outcome Hypothesis

    2. Definition > Type: Text (multiple lines)

    3. Definition > Description: Outline the hypothetical outcome to the business of this Epic

    4. Layout > Label: Business Outcome Hypothesis

    5. Layout > Group (new): Business Outcome Hypothesis

    6. Layout > Column: Left

  4. Create a new field "Non-Functional Requirements (NFRs)"

    1. Definition > Name: Non Functional Requirements

    2. Definition > Type: Text (multiple lines)

    3. Definition > Description: Outline the NFRs for this Epic

    4. Layout > Label: Non-Functional Requirements (NFRs)

    5. Layout > Group (new): Details

    6. Layout > Column: Left

For the Epic, we need to populate a new "Analysis" page:

  1. Create a new page called "Epic Hypothesis".

  2. Create a new field "Users and Markets Affected"

    1. Definition > Name: Users and Markets Affected

    2. Definition > Type: Text (multiple lines)

    3. Definition > Description: Outline the users and markets affected by this Epic

    4. Layout > Label: Users and Markets Affected

    5. Layout > Group (new): Users and Markets Affected

    6. Layout > Column: Left

  3. Create a new field "Impact Products, Programs and Services"

    1. Definition > Name: Impact Products Programs and Services

    2. Definition > Type: Text (multiple lines)

    3. Definition > Description: Outline the products, programs or services impacted by this Epic

    4. Layout > Label: Impact Products, Programs and Services

    5. Layout > Group (new): Impact Products, Programs and Services

    6. Layout > Column: Left

  4. Create a new field "Analysis Summary"

    1. Definition > Name: Analysis Summary

    2. Definition > Type: Text (multiple lines)

    3. Definition > Description: Provide a summary analysis of the Epic

    4. Layout > Label: Analysis Summary

    5. Layout > Group (new): Analysis Summary

    6. Layout > Column: Left

  5. Create a new field "Return"

    1. Definition > Name: Return

    2. Definition > Type: Text (multiple lines)

    3. Definition > Description: Provide a financial (or otherwise) return of the Epic

    4. Layout > Label: Return

    5. Layout > Group (new): Return

    6. Layout > Column: Left

  6. Create a new field "Anticipated Business Impact"

    1. Definition > Name: Anticipated Business Impact

    2. Definition > Type: Text (multiple lines)

    3. Definition > Description: Outline the anticipated business impact of this solution

    4. Layout > Label: Anticipated Business Impact

    5. Layout > Group (new): Anticipated Business Impact

    6. Layout > Column: Left

For the Epic, we need to populate a new "Delivery Strategy" page:

  1. Create a new page called "Delivery Strategy".

  2. Create a new field "Sponsors"

    1. Definition > Name: Sponsors

    2. Definition > Type: Text (multiple lines)

    3. Definition > Description: Identify who the sponsors are for this Epic

    4. Definition > Default value: TBC

    5. Layout > Label: Sponsors

    6. Layout > Group (new): Sponsors

    7. Layout > Column: Left

  3. Create a new field "Incremental Implementation Strategy"

    1. Definition > Name: Incremental Implementation Strategy

    2. Definition > Type: Text (multiple lines)

    3. Definition > Description: Identify how this Epic will be delivered incrementally

    4. Definition > Default value: TBC

    5. Layout > Label: Sponsors

    6. Layout > Group (new): Sponsors

    7. Layout > Column: Left

  4. Create a new field "Sequence and Dependencies"

    1. Definition > Name: Sequence and Dependencies

    2. Definition > Type: Text (multiple lines)

    3. Definition > Description: Identify the sequence and dependencies for delivering this Epic

    4. Definition > Default value: TBC

    5. Layout > Label: Sponsors

    6. Layout > Group (new): Sponsors

    7. Layout > Column: Left

  5. Create a new field "Milestones or Checkpoints"

    1. Definition > Name: Milestones or Checkpoints

    2. Definition > Type: Text (multiple lines)

    3. Definition > Description: Identify the milestones or checkpoints for delivering this Epic

    4. Definition > Default value: TBC

    5. Layout > Label: Sponsors

    6. Layout > Group (new): Sponsors

    7. Layout > Column: Left

  6. Create a new field "Other Notes and Comments"

    1. Definition > Name: Milestones or Checkpoints

    2. Definition > Type: Text (multiple lines)

    3. Definition > Description: Provide any other relevant notes or comments regarding this Epic

    4. Definition > Default value: TBC

    5. Layout > Label: Sponsors

    6. Layout > Group (new): Sponsors

    7. Layout > Column: Left

  7. Create a new field "Go or No-Go"

    1. Definition > Name: Go or no go

    2. Definition > Type: Picklist (string)

    3. Definition > Picklist items: No-Go, Go

    4. Definition > Description: Specify if this project is to go ahead, and scheduled in the Epic plan

    5. Layout > Label: Go or No-Go

    6. Layout > Group (new): Approval

    7. Layout > Column: Middle

  8. Create a new field "Approved By"

    1. Definition > Name: Approved By

    2. Definition > Type: Identity

    3. Definition > Picklist items: No-Go, Go

    4. Definition > Description: Track who approved the go/no-go state for this Epic

    5. Layout > Label: Go or No-Go

    6. Layout > Group (new): Approval

  9. Create a new field "Approved Date"

    1. Definition > Name: Approved Date

    2. Definition > Type: Date/Time

    3. Definition > Picklist items: No-Go, Go

    4. Definition > Description: Track the approval date for the go/no-go state for this Epic

    5. Layout > Label: Go or No-Go

    6. Layout > Group (new): Approval

For the Epic, we need to populate a new "Resourcing" page.

*_Instructions to be completed._*

For an Epic we need to create the following States (as specified by the SAFe Framework):

  1. Create a new state of Name: Funnel, State category: Proposed, Color: 1st from bottom grey (1st column)

  2. Create a new State of Name: Reviewing, State category: Proposed, Color: 2nd from bottom grey (1st column)

  3. Create a new State of Name: Analyzing, State category: Proposed, Color: 3rd from bottom grey (1st column)

  4. Create a new State of Name: Pending, State category: Proposed, Color: 4th from bottom grey (1st column)

  5. Create a new State of Name: Portfolio backlog, State category: Proposed, Color: 5th from bottom grey (1st column)

  6. Hide "Active"

  7. Hide "Resolved"

  8. Create a new State of Name: Implementing, State category: In Progress, Color: 3nd from bottom blue (2nd column)

  9. Create a new State of Name: On-hold, State category: In Progress, Color: Top orange (7th column)

  10. Create a new State of Name: Done, State category: Resolved, Color: Top green (5th column)

  11. Create a new State of Name: Cancelled, State category: Removed, Color: White

For an Epic we need to create the following Rules:

*_Instructions to be completed_*

Feature

For the Feature, perform the following steps on the Details tab:

  1. Add the existing field of "Prep Effort",

    1. Definition > Use an existing field: Prep Effort

    2. Layout > Label: Prep Effort (Days)

    3. Layout > Select existing group: Planning

  2. Add the existing field of "Prep Effort",

    1. Definition > Use an existing field: Prep Effort

    2. Layout > Label: Prep Effort (Days)

    3. Layout > Select existing group: Planning

  3. Add the existing field of "Design Effort",

    1. Definition > Use an existing field: Design Effort

    2. Layout > Label: Design Effort (Days)

    3. Layout > Select existing group: Planning

  4. Ensure "Effort" is labelled as "Engineering Effort (Days)"

  5. Add the existing field of "Test Effort",

    1. Definition > Use an existing field: Test Effort

    2. Layout > Label: Test Effort (Days)

    3. Layout > Select existing group: Planning

  6. Add the existing field of "Planning Effort",

    1. Definition > Use an existing field: Planning Effort

    2. Layout > Label: Planning Effort (Days)

    3. Layout > Select existing group: Planning

  7. Add the existing field of "Operate Effort",

    1. Definition > Use an existing field: Planning Effort

    2. Layout > Label: Planning Effort (Days)

    3. Layout > Select existing group: Planning

  8. Create a new field of "MoSCoW",

    1. Definition > Name: MoSCoW

    2. Definition > Type: Picklist (string)

    3. Definition > Description: Help prioritize this Feature for delivery by the Team.

    4. Definition > Picklist items: Wont Have, Could Have, Should Have, Must Have

    5. Layout > Label: MoSCoW

    6. Layout > Group: Classification

  9. Create a new field of "Value Area",

    1. Definition > Name: Value Area

    2. Definition > Type: Picklist (string)

    3. Definition > Description: Business = Services provided by the system to fulfill stakeholder needs; Architectural = Technical system services to implement business features that deliver solution value

    4. Definition > Picklist items: Architectural, Business

    5. Options > Required: True

    6. Options > Default value: Business

    7. Layout > Label: MoSCoW

    8. Layout > Group: Classification

  10. Hide "Personas affected" extension

  11. Hide "Log time in Harvest" extension

  12. Hide "Priority"

  13. Hide "Risk"

  14. Hide "Business Value"

  15. Hide "Time Criticality"

Create the following states:

  1. Create a new state of Name: Prep, State category: Proposed, Color: 1st from bottom grey (2nd column)

  2. Create a new state of Name: Design, State category: Proposed, Color: 2nd from bottom blue (2nd column)

  3. Create a new state of Name: Engineer, State category: Proposed, Color: 3rd from bottom blue (2nd column)

  4. Create a new state of Name: Test, State category: Proposed, Color: 4th from bottom blue (2nd column)

  5. Create a new state of Name: Operate, State category: Proposed, Color: top green (5th column)

Issues

*_Instructions to be completed_*

Mitigation (existing)

Questions

*_Instructions to be completed_*

User Story

*_Instructions to be completed_*

Tasks

  1. Hide "Priority"

  2. Create a new field of "Activity",

    1. TBC

  3. Create a new field of "Resolution",

    1. Definition > Use an existing field > Field: Resolution

    2. Layout > Group: Resolution