All,

Thanks for participating in the meeting today. Here are the action items from our conversation.

Participants: Naseer Khan (NK) Nangar Soomro (NS) Ahmed Faruq (AF) Mushtaq Ilyas (MI) Muazzam Baig (MB)

1. All Waseela-e-Taleem documents (guidelines) are to be shared with MI NK & NS 2. Payements (Rules listing etc), MND (Case Management) & Communications documents/guidelines are pending with Operations Dept. NK to follow up 3. Social Mobilization is something new (AF), it has not been considered so far in the bigger picture of all things. AF 4. Data format for 5th August field exercise to be provided by Operations once format is delivered (today) to Operations NS, AF & MI 5. Update Timelines to be communicated to all stakeholders within this week MI 6. New project plan to be detailed enough to show follow ups and meetings with Operations MI 7. Circular to all directors to only communicate via and to official e-mail addresses. MB 8. There have been new requirements for the enrolment software, therefor the software will only me made available for testing once all requirements have been accommodated. AF & MI

9. MI to be part of all communication between Operations team and MIS NK & NS

Regards, Mushtaq Ilyas

Software Project Manager Benazir Income Support Fund +92 345 5254342 Description: Description: BISP-Logo Dear Mushtaq, I am developing a document on roles and responsibilities of BISP staff with general categorization (management user, operations user etc). I hope to share this document over the weekend. The access levels need not to be defined on the basis of systems only but also on the functionality of the systems that will differentiate the two types of users. The implementation mechanism is such that each level officer (Region/division/tehsil) will be taking care of all the systems but with different access levels for different functions of the systems. The functionality wise access levels for each role can be defined only after we know about the functionality of all the systems and their sub-systems. I proposed to have meetings on specifying the requirements of systems to Director IS which in his opinion can be done only after the prototypes of the systems are ready and that the prototypes will be developed first and then discussed. This to me appears a bit unrealistic since prototypes should be based on requirement specifications and must be discussed before development. The prototypes are not for guiding the functionality of the systems but to guide on their user friendliness only. In my opinion, the approach suggested by Director IS has a potential of delay if prototypes would need to be adjusted again on the basis of specifications that will be developed afterwards, especially since discussions on prototypes will be done once they are developed and not before that. I have already shared all the available guidelines and so would once again propose to have informed discussions on the requirement specifications any time soon. The schedule of such meetings should also be proposed in the MIS deadlines document (to be shared today). I would request Director Waseela-e-Taleem also to give his direction in this regard for streamlining the activities (specifications first or the prototypes?). Please feel free to contact me for any type of support, share your views or correct me where I stand wrong. Regards,

Naseer Khan Marwat Operations Design and Planning Specialist Room No 214, F- Block, Pak Secretariat, Islamabad. Mobile: 03454408936 > Naseer, > > > > I will need the roles hierarchy based at the different regional levels. > These roles will dictate the level of access required for the following > systems > > 1. Pre-Enrolment > > 2. Enrolment > > 3. Compliance > > 4. Payments > > 5. Case Management > > 6. Monitoring > > > > Please let me know if you need more info. or input on this. > > > > Regards, > > Mushtaq Ilyas > > > > Software Project Manager > > Benazir Income Support Programme > > 131, F- Block, Pak Secretariat, Islamabad. > > +92 345 5254342 > > > > Description: BISP-Logo > > > >

Mushtaq Ilyas

mushtaq.ilyas@bisp.gov.pk

Jul 13 (5 days

ago) to Naseer, dg.ops, alliahsan, Ehtasham, ahmad.faruq, me, soomro.www

Thanks Naseer. Your desire for the MIS timelines to be shared today unfortunately cannot be fulfilled. There is a lot to consider before finalising the timelines. " This to me appears a bit unrealistic since prototypes should be based on requirement specifications and must be discussed before development" We have requirements specifications for the systems before any development in the project plan, so I am not sure where you are coming from in your concerns above. Also it is a good practice to induct feedback (gaps identified in prototypes ) into the final implementation and that can lead to re-visiting the requirements. I agree with your suggestion for discussions and can promise that we will have these sessions very soon. Cheers,

Naseer Khan

Jul 14 (4 days ago)

to Mushtaq, dg.ops, alliahsan, Ehtasham, ahmad.faruq, me, soomro.www

Dear Mushtaq, Thanks for your response. Unfortunately I could not read your separate email on MIS timeline that I received while composing my last email and that is why I could not remove the today's deadline part from my last mail. The deadline reminder was sent mainly to emphasize on the need for timely provision of deadlines as DG (Operations) desired on Thursday to discuss it with both Waseela-e-Taleem and MIS teams on Firday sometime. The excerpt of my email that you have raised a question upon was succeeded by "I proposed to have meetings on specifying the requirements of systems to Director IS which in his opinion can be done only after the prototypes of the systems are ready and that the prototypes will be developed first and then discussed." The existence of requirement specifications in the Project Plan was not questioned at all but the timing was (specifications or prototype first?). My discussion with Director IS ended up with an understanding to discuss the requirements (abstract level may be) only after the development of prototypes. Moreover, the functional access levels (not talking about the desired system access levels) can also be defined through this step done first. Re-visiting is a good thing to improve the process but not to re-start it simply because appropriate consultations prior to development are not done as was in the case of enrolment software for the soft launch which once developed was not exactly in accordance with our requirements. These issues were raised by my colleague (Mr. Soomro) as well and I raised them for better understanding, being focal person for MIS from Waseela-e-Taleem side. Your resolve to have meetings/discussions during the development process is

much appreciated. I hope you do not take any of my opinions personally and understand my professional obligations. I myself fully understand the limitations of new MIS team in taking up the task to fulfill our operational needs too soon since you guys have joined the team very recently and MIS team was short of desired team members before.

Ahmad Faruq

9:30 AM (26 minutes ago)

to Naseer, Mushtaq, dg.ops, alliahsan, Ehtasham, me, soomro.www

Dear Naseer,

The Process document(s) being shared by Waseela-E-Taleem are the 'requirements'. Whatever you want to specify that's the place for you.

Subsequent deliverable for Ops is prototype & subsequently actual applications:

Idea of sharing Prototype is to give the end users an instant Know how of how of what is coming, both in terms of Functionality & UI.

The requirement(s) doc are for IS internal sub teams, Of course these are present all the way. If you want to interact with those you are welcome.

Best regards