LACE (CCSQ Lean Agile Center of Excellence)

Page tree

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Standard Project Template (SPTDP) Sample Project: Standard Project Template Development Project - QualityNet JIRA (cms.gov)

Create Boards

1) Create initial board: “Program” Backlog (All Items)” (with the standard setup user cannot see any new backlog items that are created)

Move all unmapped statues to the associated columns (per status category):


2) Create a Kanban board for the Feature backlog: ‘Program’ Feature Kanban

    • Update project filter query to: project = ‘xyz-project’ AND issuetype = 10000 ORDER BY Rank ASC
    • Configure the following columns with statuses


Additional Configurations:

  • Add Feature size to Feature:

       

  • In Issue Detail View, Add ‘Total Story Points’ (same function as custom field “Story Points Sum Up”)
  • Create new Definition of Ready and Definition of Done checklist fields
    1. Discuss options for a global prepopulated checklist
    2. Can there be different prepopulated checklists based on issue type
    3. Review creation/edit rules for checklists
  • Add DoR and DoD checklists: Feature, Story, Enabler

     

  • Add ‘Developer’ & ‘Tester’ to Story, Enabler, Bug, Defect
  • Make Estimate filed available on User Story (edit mode)


Custom Configuration Requests (Do's & Dont's)






Project Setup - Initial Questionnaire


Create Project Boards

1) Create initial board: “Program” Backlog (All Items)” (with the standard setup user cannot see any new backlog items that are created)

Move all unmapped statues to the associated columns (per status category):


2) Create a Kanban board for the Feature backlog: ‘Program’ Feature Kanban

    • Update project filter query to: project = ‘xyz-project’ AND issuetype = 10000 ORDER BY Rank ASC
    • Configure the following columns with statuses


Work Structure

Value Delivery

The entire goal of the work processes is to deliver value.

"Working software is the primary measure of progress." - Agile Principle #7 1

Once the team has completed work (per the Definition of Done 1), they show their value output to Product Owners, Product Management, Stakeholders, and Customers. All valuable work that helps to solve their problems is included in this demonstration and review. That includes, but is not limited to, documentation, marketing materials, UI designs, user personas, and, of course, any working software.

The events for review are Iteration Review 3 at the Team Level and System Demo 4 at the Program Level.

Iteration Review

At the end of an Iteration, the Agile Team demonstrates completed functionality and value output to showcase their work to interested stakeholder and/or customers and solicit feedback. This is the Iteration Review, sometimes referred to as the Sprint Review.

System Demo

Just as the Agile Team demonstrates completed functionality and value output at the end of the iteration, the ART must demonstrate all of the Teams' integrated work in the System Demo.

Foundational Values

All of the above practices and processes are based on the principles and values of Lean Thinking, Empiricism and Metrics, and The Agile Manifesto.

Empirical Data/Metrics

Without empirical data and metrics, decisions will be made with incomplete or erroneous information. "Empiricism asserts that knowledge comes from experience and making decisions based on what is observed."

Lean Thinking

Based on Lean Thinking in manufacturing, we can eliminate waste by mapping our processes and identifying areas of improvement. "The Lean-Agile Mindset is the combination of beliefs, assumptions, attitudes, and actions of SAFe leaders and practitioners who embrace the concepts of the Agile Manifesto and Lean thinking. It’s the personal, intellectual, and leadership foundation for adopting and applying SAFe principles and practices." "Lean thinking reduces waste and focuses on the essentials."


  • No labels