Category Archives: Scrum

Capstone Project: Week 3 Reflections

Yet another week here and gone. This weeks reflections will be fairly brief due to it being the end of our sprint and having a weekend with nothing to work on. However, we did have a sprint retrospective this week due to our sprint completion! The retrospective went well. Our team has really great communication and that has helped us, so these retrospectives are just re-caps of things we found during the week.

One of the major issues we discussed was with our daily stand-ups. Due to us having to all do them remotely there leaves a lot open for loosely worded statements. We were using a lot of “I’ll try” or “I might get it done” and we wanted to clear up this language and be more precise. We found that two things happened when we became more precise.

  1. Others trusted what we said and knew we were going to get done what we said.
  2. We held ourselves personally accountable to truly get the things done that we said we were going to.

These two things I feel are very important for any scrum team!

We did our first real sprint planning today and I am very excited to start working with the AMPATH code and seeing what true professional software looks like!

From the blog CS@Worcester – Tyler Lundstrom by CS@Worcester – Tyler Lundstrom and used with permission of the author. All other rights reserved by the author.

Yay, Scrum!

For this semester, we will be collaborating with OpenMRS and AMPATH for the entire duration of the course to possibly help develop some type of new software that the association can use in their medical systems. That alone in itself is extremely exciting and I can’t wait to really begin diving into the hands-on programming of whatever software it is we will be developing because this will be the first time I am doing something that is career-based related in the real world.

What’s even more exciting is the new framework of Scrum that I have recently been introduced to. The idea of Scrum is to divide up the development cycle up into 1 to 2 week intervals known as sprints where there are goals and objectives set for each sprint that the team focuses on completing before moving onto the next sprint into the rest of whatever needs to be developed. I don’t really want to dive a lot into how Scrum actually works because I’m sure you can look it up online for a better understanding of it if you want but I am really looking forward to incorporating this framework into our collaboration with OpenMRS and AMPATH and gain further exposure to experiences I will most likely be using once I get a job as a software developer.

While I was job hunting, there were definitely a handful of companies and corporations who are looking for employees with experience in Scrum so hopefully I can add that to my resume after this course!

CS 448 Week 1 Blog (January 17 – January 23)

From the blog CS@Worcester – Tan Trieu's Blog by tanminhtrieu and used with permission of the author. All other rights reserved by the author.