Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Draft phases for this project

    1. Monitoring list:

      Stage 1:

    2. Bug-Fixing of exiting features from previous phase

    3. Demo & Analysis of missing features

    4. I - Bug fixes and missing functionalities from initial phase

      1. In relation to the WB feedback, we should spent some time in adjusting the existing modules into the requirements - https://docs.google.com/spreadsheets/d/1sEJ2QBiPEO7MX9EnblBM0Cplq9L6mtOv/edit#gid=417237253 transfer montroing list to jira

      2. Based on the previous requirements we should define the 2nd phase starting point

      3. Main goal - before new development starts  we need to adjust currently existing modules to the MVP requirements

    5. Stage I a - Previous development analysis

      1. SolDevelo to prepare a detailed demo for each of the delivered modules (ideally based on the WB/GIZ feedback with what is unknown - it will make these demo effective)

      2. Existing modules UML diagrams to visualize the business process - this was missing in the initial phase

    6. Stage II - New development requirements

      1. Gathering the priorities for new development

      2. WB - to prepare the business requirements and diagrams for the visualization

      3. SolDevelo to prepare a new migration plan (to be discussed on a daily basis before the final plan is ready).

        • Note: The plan may be changed during the development but it’s crucial for all involved in the project to be on the same page before development starts

    7. Deliverable - Inception report, Roadmap, Development plan

    8. Stage III Development

      • Strong cooperation - daily meetings (stand ups)

      • Backlog refinements - with WB participation when the tickets are clarified

      • Longer sprints

      • Cooperation in defining Sprint Goal

      • Additional meeting for requirements clarification

Action items

  • Artur Lebiedziński to prepare a example of the ticket monitoring structre in Jira

  • Artur Lebiedziński to create a reccuring meetings and send the invitation

  • malike Andrea define the priorirites within each modules - so the point when we can consider the feature as done

Additional resources

Module Narratives openIMIS-coreMIS

...