Sync2.0 Sprint for UgandaEMR

Hi @c.antwi thanks for your concern

The sprint was completed, although, we were not able to tackle most of the tickets in the sprint due to technical difficulties in reproducing the reported bugs and working around the code base and so on.

We had a retrospective meeting, and most of the devs needed more guidance technically how to go about their blockers but we couldn’t get much or reliable information for the same.

Now there are several issues that led to that

  • Sprint2 module i would say is slightly a complex module to a new dev, and it would be very hard for a new dev who is not yet familiar with openmrs APIs to understand the code in there. for example it was basically built on fhir , openmrs rest-framework , ui-framework ,serialization…and really those are abit complex openmrs frameworks for a new dev

  • Most of the devs added as team members were new , in this i mean not yet familiar with our openmrs frameworks and APIs , so it was very hard for them getting around those tickets

  • The tickets were described from a users point of view completely ,and unless some one is familiar with some of our frameworks , it would be very hard for them knowing what to do.

  • @ssmusoke has been a little scarce to give more techinical guidance to questions that have been raised by some members .
    I have a been a little busy with some of ref app features but i have raised two PRs and would keep on working on more, though so far there has not been any single comment made to the Prs i raised cc @dkayiwa

Way forward …

  • Either our new dev team mebers would have to familiarize themselves with our openmrs frameworks ,or we can add more dev2s and dev3s as team members cc @odorajonathan

  • @ssmusoke should be more readily available to give more techinical guidance so that even new devs who arent more familiar with some of our frameworks can get to know what to do

cc @c.antwi @dkayiwa @ssmusoke @odorajonathan

3 Likes

Yes @mozzy I highly agree with you on adding more devs on the team to help with some of the more complex tickets.

I thought the Soldevelo team was willing to contribute to the sprint, but am not sure why we didn’t have their expertise on this, cc @jslawinski

1 Like

But did the team go through all the existing documentation on the wiki? Were we specific and clear with exactly what help we were looking for? Were there product owners identified who could be called on to provide that technical guidance ? @odorajonathan @mozzy I will take this up at the next PM call Aug 26th 2019. Can the project lead join us on that call?

@c.antwi The team needed more support from a more experienced developer who was not available at the time. I only had sufficient bandwidth to play the role of product owner.

Until additional support is gotten in that area, all these efforts will not be productive and will keep failing

1 Like