Sprint 1: DRMFSS Feedback
Date
Friday, 28 June 2013
Attendees
- DRMFSS
- Negussie Kefene
- Askale Asaye
- Makeda W/hiwot
- Hailu Ankiso
- Yehuwalashet Haile
- Zewde Bekele
- Tesfaye G/Wolde
- Tewodros Genanaw
- Yonas Daniel
Sprint Focus
- Regional request (Early Warning) - Implementation of monthly regional requests for relief program. Requests then passes through different stages of approval process before Relief Requisition (RRD) document is produced
- Operational reports (DRMFSS Hubs)
- Stock status Report
- Dispatch Report
- Receiving Report
User Comments
| Who | No. | Comment | Response |
|---|---|---|---|
| Abdulkerim | 1 | Is there a possibility to give access to DRMFSS staff to get their hands on the product being demonstrated during a sprint. If it is possible for them to start trying the product at the end of each sprint without waiting for the release date | During the end of each release (three sprints) users will be able to get there hands on a working and deployed product. |
| 2 | It is a good thing that the release touches for the most part all functional units within DRMFSS | ok | |
| Zewde | 3 | We would like to start using the demoed system as soon as possible especially the ability to check stock status at the hub level | See comment #1 |
| 4 | The reports are a good start but how much of our needs for reporting can you address? There are requests which come both from within DRMFSS and from donors with quite an extensive list of reporting requirements such as grouping and summary | ||
| 5 | How can our Ad-Hoc reporting needs be addressed using CATS? | ||
| 6 | Upon allocation of hubs, the system should be able to show stock status of each hub | ||
| Negussie | 7 | Are we going to provide access to Regions to add the monthly request from the beginning or do we need someone at federal level to encode the data into CATS? | As per the task-force meeting on 06/05/13. See Regional Governments |
| 8 | Are you clear with the relationship and/or differences between Round and Month during RRD allocation? It is not always that the two will match and we can not say that they are consistent across all regions. This difference can be seen on the HRD document whereby we have regions which got 8 rounds in the plan while others have only 5 | Clarified in 2013-07-11: Allocation 'Round' Vs Allocation Month | |
| 9 | There are currently have more than 300 Woredas and 1000+ FDPs we are working with. What will happen if we add additional FDPs or Woredas? Will CATS be able to accommodate that change? | Yes | |
| 10 | Have you considered Fast-on-set allocation and Non-Food commodities too? | ||
| 11 | Can we come and attend Daily Standup meeting with the team? | Everyone is welcome to attend the daiy standup, but only the development team is permitted to speak | |
| 12 | Will CATS allow a single person do all of the allocation (regional, resource, dispatch) if we wanted to do so? I mean the Early Warning Logistics Planner can technically perform all of the tasks in dispatch allocation such as validating number of beneficiaries in the request against the HRD, assigning hub/location for dispatch, checking stock balance and preparing RRD if CATS somehow allow him/her to do so? | The system is divided into a number of "Roles", based on our understanding of the current DRMFSS structure. If DRMFSS wishes to assign multiple roles to an individual, this can be done | |
| Yehuwalashet | 13 | Can we have access to Free Stock report so that we will have a clear idea of what resources we are allocating? | |
| 14 | In HRD only zone, Woreda and number of Beneficiaries are needed | ||
| 15 | It will be very dangerous if we allow everyone to manage and maintain the list of FDPs and Woredas in CATS. Someone (ICT or Case team co-ordinator) should be responsible for maintaining that list | This is correct. DRMFSS should nominate a role to undertake this task. However, it is recommended that a business user, not an ICT person be responsible for this. | |
| 16 | Upon allocation of hubs, the system should be able to show stock status of each hub | ||
| Askale | 17 | In reply to what Nigussie has said regarding the EW Logistic Planner being able to do all of the dispatch allocation [Comment #11]; it would not be fair to put all of the tasks in dispatch allocation on a single individual but it wouldn't hurt to have access of hub information such as free stock | The allocation of roles to an individual will be the responsibility of DRMFSS |
| 18 | Report Should be per round ,zone ,Woreda and FDPs | ||
| Tesfaye | 19 | It is very important that reports such as stock report/free stock be available to anyone who is doing any task related to resources | |
| 20 | We should have a clear terminology throughout the CATS to avoid confusion from users. e.g. Which one to use 'Send to logistics' or 'Post' | CATS Change: “Send To Logistics” link should be renamed to “Post [to logistics]” | |
| 21 | How are we planning to manage system wide lookup records? | [More information needed] | |
| 22 | Do we have an exhaustive list of lookups for CATS? | The "Admin" menu option in CATS shows the full list of available lookups | |
| 23 | Reports should be role based (Demand based reports with a different filter criteria option) | ||
| 24 | How are you planning to address reports?
| Reports are definitely a key part of CATS:
| |
| 25 | Have you considered audit-log and activity logging throughout CATS? If so will it also address data changes by users or versioning of records through time? | All changes to data will be recorded in an audit log | |
| Other (unattributed) | 26 | Report organization view should be revised | |
| 27 | Upon allocation the system should include edit functionality after allocation |