Reminders of steps to be carried out
Prerequisites

- Decision-support project in agile mode

Comprehensive project analysis

Defining the need

  • Conduct an interview (there will be no client to dialog with in the context of your project)
  • Write a user story: this will lead to the creation of the Product Backlog
  • Identify the non-functional needs (dashboard format/resolution, color code, updating frequency, etc.)

Managing the project

You will need to carry out your project in agile mode, which imposes certain requirements:

  • the drafting of an overall Product Backlog for the project
  • the use of a project-management tool, such as:
    • Trello or Backlog, which are relatively simple tools based on using a Kanban board to monitor tasks
    • Taiga or Jira, which are more complex tools enabling more detailed monitoring of your project
    • Any other tool whose relevance you can justify. This could be an even simpler resource such as a spreadsheet, although this would require a very rigorous approach to its use (which could require more organizational work than simply using one of the existing tools)
  • For each sprint, you must also:
    • precisely define the breakdown of each user story into tasks (although certain cross-cutting tasks may be common to several user stories), and the allocation of these tasks
    • write a several-line report on each daily meeting (daily meetings are not required in our context; you can hold them less frequently)
    • write a Sprint retrospective report
    • Update the quiafaitquoi.xls file with the authors of the tasks to reflect what was really done (rather than what had been planned)

For each Sprint

Defining the need

  • Discuss with the client (new interviews, focus groups, etc.)
  • Specify the user stories: this will lead to the creation of the Sprint Backlog

Specifications

Design

  • Produce a dimensional schema
    • Define the process
    • Define the grain of the fact table
    • List the facts
    • Define the dimensions
    • Ensure the conformity of the dimensions and specify the bus matrix
    • Identify the types of changes for the dimensions
  • Produce the logical datamap
  • Produce test specifications

Implementation

  • Create the databases (optional in the context of your project)
  • Create the ETL processes
  • Create the dashboards

Finalization