Course Outline

1. "Scrum Framework" - Organizing the Project and Working with Business Value for Government

  • Organization of work with requirements in Scrum: The Product Backlog Refinement Process
  • Artifacts in Scrum: Product Backlog (a register of requirements), Sprint Backlog (a register of tasks), Increment (a working business value)
  • User Story Map - An approach to effectively build requirements for government projects

2. Presentation of a Sample Process of Working with Requirements in an Application for Government

  • From registration of customer needs through the creation of vision, Product Backlog, and Sprint Backlog on the example of a project to implement an application supporting selected government business processes.

3. Identification of Project Target Groups - Personalization of Stakeholders for Government

  • Stakeholders, project client, and end users
  • Multi-generational considerations and their impact on identifying the needs of government customers
  • Workshop: Designing requirements for user projects - defining project personas in the context of the multigenerational market for government

4. Formulating the Product/Project Vision for Government

  • Project goal and vision
  • Workshop: Creating a product/project vision - Canvas model as a basis for delivering business value based on the needs and context of the situation at the government customer

5. Defining Project Quality - Definition of Done for Government

  • Identifying project quality criteria
  • Workshop: Creating a definition of project quality - Definition of Done for government projects

6. Identifying the Business Value in the Project - Working with the Requirements Register (Product Backlog) for Government

  • Organization of work with Product Backlog - transferring customer needs into high and low-level requirements for government
  • Product Backlog integrated - common requirements and requirements for specific "domains" in government operations
  • Workshop:

o Preparing a requirements registry - epic, theme, user story
o Product backlog in process and product approach for government projects
o Release planning - project roadmap for government initiatives

7. Identifying the Business Value in the Project - Requirements and Acceptance Criteria - Creating User Story Map for Government

  • Identification, definition, decomposition, and prioritization of requirements - tools and techniques such as Richard Lawrens, Elephant Carpaccio exercise for government use
  • Workshop:

o Defining requirements - identifying requirements in the user story formula
o Measuring requirements and accounting effectiveness - identification of acceptance criteria for user stories in government projects
o Prioritization of requirements based on the needs of the project customer in government settings
o Requirements transfer - ensuring clear communication of customer needs into transparent user stories for government

8. Accounting for Business Value for Government

  • Requirements, tasks, presenting business value, and increasing efficiency for government projects
  • Workshop:

o Decomposition of requirements into tasks
o Simulation of presentation of requirements and deliverables by the team in a government context

9. Refinement - Summary of the Workshop in the Form of an "Action Plan" for Government

  • Workshop: Summary of the training in the SSC formula using facilitation techniques for government teams

o Start - what I will implement as a new good practice
o Stop - what I will stop
o Continue - what I will continue to apply in government projects

Requirements

The training does not require any additional preparation for government participants.
 14 Hours

Number of participants


Price per participant

Testimonials (2)

Upcoming Courses

Related Categories