Order Entry UI sprint 5

Owned by Flavia Nshemerirwe
Last updated: Jun 10, 2018 by Lanre Lawal
2 min read

General Information

Team Lead: Daniel Kayiwa

Sprint Lead: Flavia Nshemerirwe



Timeline

Start Date: May 22, 2018 

End Date: Jun 5, 2018 

Participants

  • Flavia Nshemerirwe

  • Fredrick Mgbeoma

  • Lanre Lawal

  • Geoffrey Asiimwe

  • Osaze Edo-Osagie

  • Betty Kebenei

Sprint Goals

The main goal of this sprint is to implement the feedback received from the community and fix any identified bugs in the due course.

The goal has been sub divided into several tasks:

  1. Filter drop downs by first letter.

  2. Widen drug prescription field boxes.

  3. Fix inconsistent date formats.

  4. Fix form persistence when switching between inpatient and outpatient tabs.

  5. Improve on the wording of identified buttons and field labels.

  6.  Fix any bugs identified as the application is being tested.



Sprint Dashboard

key summary type created updated due assignee reporter priority status resolution

Unable to locate Jira server for this macro. It may be due to Application Link configuration.





How To Participate

Add your name to the list on this wiki page (with any comments about your availability). If you want to join after the sprint has started just join the IRC channel mentioned above and say hello.

The general process:

  1. New to OpenMRS sprints? Want help getting started? Join IRC and say "???": I'd like to participate in the sprint!". If you get no response, just ping any of the above sprint participants as per the IRC tips at http://en.flossmanuals.net/openmrs-developers-guide/support/

  2. Pick a ticket from the available tickets in the top-left of the sprint dashboard page at:

  3.  

    • Make sure it does not depend on a ticket that is incomplete.

  4. If you have any questions about the ticket, ask on the group chat.

  5. Do the ticket. See our HOWTO for git. Sprint specific git HOWTO for devs with push rights: whatever works for you :-) If you don't like pull requests, don't send them. Commit and push directly to the main repo. If you do like pull requests, fork the main repo and send pull requests, but merge them right after. My favorite way is to work on the main repo, but create local branches (without pushing them to the main repo). Merge branches locally to the master and push to the main repo.

  6. Join the daily scrum to share your updates





During Project Notes for the sprint

The team was able to complete all the tasks on the board within the first week.
For week two, new bugs were identified and we shall use this week to test the application more and fix any identified bugs.

Sprint Retrospective:

What could have been better?

  • Communication was good on both ends, the team lead and the team were aware of what was happening.

  • The team took the initiative to come up with tasks when the tickets got done.

  • The team collaborated on various tasks very well.

Areas of improvement.

  • Time management for the sprint planning meeting and demos.

Resources