...
Draft phases for this project
- Monitoring list:
Stage 1:
Bug-Fixing of exiting features from previous phase
Demo & Analysis of missing features
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
Based on the previous requirements we should define the 2nd phase starting point
Main goal - before new development starts we need to adjust currently existing modules to the MVP requirements
I - Bug fixes and missing functionalities from initial phase
- Monitoring list:
Stage I a - Previous development analysis
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)
Existing modules UML diagrams to visualize the business process - this was missing in the initial phase
Stage II - New development requirements
Gathering the priorities for new development
WB - to prepare the business requirements and diagrams for the visualization
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
Deliverable - Inception report, Roadmap, Development plan
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
...