My group was working on an Issue ticket, RAD-159, where we had to delete unused code in two files. It appeared to be a simple task at first, but through a lot of confusion, we had to redo our deletions multiple times. The tickets description of what to do was not specific enough, and even after asking for help, we were still confused. This shows how important clarity of instruction is when designating work to other people. This ticket should have taken a day at the longest, but it was extended for long periods of time due to having to ask numerous questions and then having to get our group together after each answer. We did finish our issue though, and we are hopefully going to have our revisions accepted. In the future, I will know to be as thorough as possible when writing directions for other people.
Worcester State University Computer Science Department
- 5/5/16 Finished & Final Thoughts…
- 3/18/16 Chapters 4 & 5
- 3/3/16 The ICU and You!
- 2/24/16 Open MRS and Chapter 1
- 1/26/16 Starting out in Software Development Capstone
- Last Class
- And it’s over: OpenMRS Final Thoughts
- OpenMRS Radiology: Finished Issue
- OpenMRS: A New Issue
- PAX East 2016: VR in a Software Development Environment
- My Very First Pull Request
- Post from week 4/25-4/27
- Issue Complete?
All posts syndicated from other blogs are the property the original author, are subject to the copyright and licensing terms of that blog, and are used here with permission of the author.
All posts original to this blog are licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.