Top Menu

Jump to content
Home
    • Projects
    • Work packages
    • News
    • Getting started
    • Introduction video
      Welcome to Government of Rwanda Projects
      Get a quick overview of project management and team collaboration with OpenProject. You can restart this video from the help menu.
    • Help and support
    • Upgrade to Enterprise edition
    • User guides
    • Videos
    • Shortcuts
    • Community forum
    • Professional support
    • Additional resources
    • Data privacy and security policy
    • Digital accessibility (DE)
    • OpenProject website
    • Security alerts / Newsletter
    • OpenProject blog
    • Release notes
    • Report a bug
    • Development roadmap
    • Add and edit translations
    • API documentation
  • Sign in
      Forgot your password?

Side Menu

  • Overview
  • Activity
  • Work packages
  • Boards
  • Project library
    • Table of contents
      • Expanded. Click to collapseCollapsed. Click to showProject library
        • Expanded. Click to collapseCollapsed. Click to show00 Scope
          • Hierarchy leaf00 Project charter (empty)
        • Expanded. Click to collapseCollapsed. Click to show10 Requirements
          • Hierarchy leaf00 Requirements assessment
          • Hierarchy leaf10 Requirements traceability matrix
        • Expanded. Click to collapseCollapsed. Click to show20 Stakeholders & Communication
          • Hierarchy leaf00 Stakeholder analysis (empty)
          • Hierarchy leaf10 Communication plan
        • Hierarchy leaf30 Team & Resources
        • Hierarchy leaf40 Architecture
        • Hierarchy leaf50 Reporting
        • Hierarchy leaf60 Risks (empty)
        • Hierarchy leaf70 Contract Documents
        • Expanded. Click to collapseCollapsed. Click to show80 Deliverables
          • Hierarchy leafSome deliverable
        • Expanded. Click to collapseCollapsed. Click to show90 templates
          • Hierarchy leaf010 project charter
          • Hierarchy leaf020 reporting template
          • Hierarchy leaf030 Default ToR for Government of Rwanda IT projects
        • Expanded. Click to collapseCollapsed. Click to show95 Standards & Processes
          • Expanded. Click to collapseCollapsed. Click to show00 PM methodology at RISA
            • Hierarchy leafMeeting Structure
          • Hierarchy leaf01 Standards for the "Definition of Done" (DoD)
          • Hierarchy leaf04 Severity of Incidents
          • Hierarchy leaf05 Acceptance procedure
          • Hierarchy leaf10 Architecture principles
          • Hierarchy leaf20 Service Digitization Guideline
          • Hierarchy leaf30 Service request process
          • Hierarchy leaf40 Test Management
          • Hierarchy leaf50 Version Managment
          • Hierarchy leaf60 CI/CD
          • Hierarchy leaf70 Contract Management
You are here:
  • Project library
  • 95 Standards & Processes
  • 00 PM methodology at RISA

Content

00 PM methodology at RISA

  • More
    • Print
    • Table of contents

latest version of this document always under:

https://projectmanagement.risa.rw/projects/risa-template-scrum/wiki/00-pm-methodology-at-risa

Development Methodology at RISA

The project management methodology uses the SCRUM approach as proven agile methodology. This methodology will be used for project management inside the overarching iterations. The following main artefacts/roles will be used.

Overarching iterations

Solutions should be implemented in iterations. Each iteration would be expected to take 2-3 months.

Sprint

Each sprint is a time boxed development phase which will be used to deliver ready to use products. The intention is, to add small features and user stories in each sprint to deliver an incrementally improved product. Current sprints at RISA use a one-week time box. The duration of the standard sprints can be adjusted as part of the retrospective.

Feature/User Story

Features and user stories are the artefacts which define the deliverables inside a sprint. They need to be described and documented. The team has to agree on the “definition of done” for an agreement of completion of the respective artefacts. The difference between “user story” and feature for RISA is mainly the distinction between deliverables with a concrete impact on users (resp. user stories) like implementation of a specific dashboard or workflow or deliverables with no specific impact on users (resp. features) like implementation of a core data model.

Epics

Epics can be used to structure Features or User Stories when they cover more than one sprint. Epics should not be assigned to a specific sprint.

Story Points

Story points give a rough estimation for complexity of user stories. They should not be confounded with effort as the y cover risks as well. At RISA a very simple approach for story points will be used:

  • small = 1 story point - it can be done with low risk in one day by the current team
  • medium = 3 story points - it can be done with low risk in three days by the current team
  • large = 7 story points - it can be done with low risk in one week by the current team
  • extra large = 14 story points - it can be done with low risk in one sprint by the current team

For the evaluation of story points the closest value should be chosen.

Backlog

The Backlog covers the list of all features and user stories which are in scope or will be in scope for implementation. It acts as the pipeline for to be implemented artefacts.

Scrum team

The scrum team is the team which will deliver the final solution. As per the currently planned (to be revised setup) it consists of:

  • Implementation team of the consulting team
  • other stakeholders as per stakeholder analysis

Product owner

The RISA project manager acts as the product owner for this project. He will provide priorities for project artefacts and finally accept or reject the implemented features or user stories.

Project management tool

RISA uses “OpenProject” for project tracking and planning. This system shall be used for project planning and reporting by the vendor. projectmanagement.risa.rw

CI/CD Environment

RISA uses Gitlab for versioning and CI/CD. This should be used as a code repository. http://repository.risa.rw

Loading...