Sprint 4 Reflections

In this sprint we were given actually issues to fix for AMPATH. We were also introduced to JIRA which is a tool to help organize bugs and issues that need to be fixed. It also helps organize who is working on what issue. After getting used to JIRA we were assigned an issue as a group. We worked on this issue but could not find a solution. JIRA is a very helpful tool to organize issues and bugs. The only thing I would change about the last sprint is trying to work on bugs together more than independently, I know this is an issue because we do not have much time in class but it would be ideal.

From the blog CS@Worcester – Software Testing by kyleottblog and used with permission of the author. All other rights reserved by the author.

Reflections on Learning and Work Products, Sprint 4

For our fourth Sprint for the OpenMRS AMPATH project, our team came together and talked about how to tackle the issue in the Ampath system; which was called NGPOC-185. Since we had already figured out what we had to do, we broke up the issue into sections and told each team member to look into what needed to be done and pick which section they wanted. This took a lot longer than it should have due to snow storms, multiple people being sick, and spring break.

The part that I decided to select for fixing the issue was creating a pop-up box that would confirm if a user wanted to leave a page if they were in the middle of editing a form and pressed the logout button. For this I looked into the Materialize CSS framework that Angular 2 uses. One of my teammates was helpful enough to post this link in our Slack channel so that I could read up on it. However, over spring break, one of our teammates found out that we had miss interpreted the issue that we had been given. Due to this, it seemed that I no longer needed to look into Materialize since there seemed to already be a box that popped up for this. The issues instead seemed to be that even when people pressed logout from a form that they were editing, they weren’t properly returned to the login screen. We had misunderstood because we were on the wrong form page. This realization made the issue a whole lot easier and less intricate than our team originally thought. (Moral of the story always ask for more clarification and find the specific page they found the issue on.

After finding this out, we decided at our end of Sprint review to make it so that only 2 or 3 teammates work on this issue, and have the rest of the team make pairs to pick other issues to work on at the start of the next Sprint.

From the blog CS WSU – Techni-Cat by clamberthutchinson and used with permission of the author. All other rights reserved by the author.

Sprint 4 Reflection

This sprint started off well, then we experienced how the description of an issue don’t always convey the full story. Our team “finished” what we needed to do on the issue that started in sprint 3 and carried over to this sprint. The issue we chose had to do with the location of a button on the screen. The description read, “Users are requesting if the back to drafted form button can be moved to a more convenient place for easy navigation e.g near the control menu.” With this description in mind one of the team members moved the button. I then merged the change with the latest version of the AMPATH project, set up Travis-CI, and deployed the change. After program built on Travis-CI we put in a pull request. We received a response the next day stating that they would actually like the button to stay in a fixed location on the screen while scrolling like the top bar and side bar. I believe this was a good example of the importance of communication

From the blog CS@WSU – :(){ :|: & };: by rmurphy12blog and used with permission of the author. All other rights reserved by the author.

Capstone Project: Sprint 4 Refelction

This sprint reflection will be a brief one. Unfortunately for the majority of this previous sprint (8 or 9 days) I was sick. I was so sick I couldn’t really move off the bed. So unfortunately I missed out on almost the entire sprint. My team was very flexible with me being down and they were able to work around that.

Once I started feeling better I began playing some catch up with the group, communication to me teammates to see what I’ve missed and figure out where they were at. We are working on an issue in the Ampath system (NGPOC-185). Initially when we took the issue we assumed we knew what the issue was talking about. However, after I started feeling better I started testing some things out in the Ampath POC system. What I found was our initial thoughts on the issue were completely wrong! This was extremely unfortunate because the team had put in a lot of time to find a good fix to what we thought the problem was. The lesson learned here for sure was; if there is ANY doubt in your understanding of an issue, get clarification!

We concluded our sprint with a retrospective. The main thing we discussed was our failure in this area, and how to avoid this in the past. We also discussed how we were going to make up for lost time. So moving forward we’ve decided that we are going to work in pairs. The issues seem to be easy enough that 6 people to 1 issue is overkill. This should allow our team to move forward and begin progressing and be able to increase the velocity of our scrum group.

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.

Sprint 4 Reflection

In Sprint 4 we finally got our first issue assigned. Unfortunately, our first issue (NGPOC-183) was rather difficult. It took us several days to try and understand how to tackle it and we ended up not being able replicate the problem on the test server. We had posted questions on the issue in JIRA and reached out to the developers on Slack but were not able to get any clarification or guidance. Although this issue has been a dead end so far I did get gain some knowledge in the code base and have better understanding with how the location feature works in the AMPATH dashboard. Right before break our group decided to take on a new issue (APTS-296) but we have not made much progress with it yet. Aside from our issues in JIRA pulling changes from the AMPATH repo as a remote upstream always seems to create a lot of conflicts and problems connecting to the test server. It hasn’t been anything we haven’t been able to work through but does slow progress down. We find it better to pull in changes frequently to make sure we are up to date and our changes will cause as little conflict as possible if we can get to a pull request. Looking back at the last sprint we did what we could for our first issue but the lack of further guidance slowed us down and kept us from any measurable progress. Looking forward we hope to make considerable progress on our new issue and move towards our first pull request. As of right now the team is still working well together and we aren’t going to adjust our velocity for the next sprint.

From the blog CS@Worcester – Software Development Blog by dcafferky and used with permission of the author. All other rights reserved by the author.

Sprint 4 Retrospective

Sprint 4 was, I think, more productive than the previous Sprints. We actually got the NGPOC-184 issue solved. And I am thinking of picking one more issue to work on. So after this semester, hopefully, we as a team would have solved three issues.

The problem I had throughout this and previous sprints is that we are moving at a snail’s pace. The reason for that is we are all new to Angular and some of us are not able to learn Angular fast enough or not able to put in more time. It is very fustrating that we are moving so slowly. One issue in 2 months? Wow!!

From the blog CS448 – The blog about software by Sudarshan and used with permission of the author. All other rights reserved by the author.

Retrospective Sprint 4

Sprint 4 was partially overrun by spring break causing a lack of progress. However, our team was able to fix our problem and make our first push. That push was sadly not accepted because the problem has been updated with some new information. The team is back to the drawing board to find the prime location for this button before we make our next push. On top of that we picked up two more problems to tackle this sprint. I believe we are going to split into pairs to be more efficient with our time. On a different note, our team’s attendance significantly improved leading to a better review sheet at the end of the sprint. We are definitely progressing as a team.

From the blog CS@Worcester – Kyle Polewaczyk by kpolewaczyk and used with permission of the author. All other rights reserved by the author.

Software Craftsman 3+4 Week 9

Software Craftsmanship: 

“Software Craftsmanship is about professionalism in software development”. It is about an approach to software development that puts emphasis on the coding skills of the software developers themselves. He speaks about Software Craftsmanship Manifesto where one not only creates working software or not only responds to change yet creates well-crafted software and constantly adds value.

The Software Craftsmanship Attitude:

This chapter stresses the importance of continual learning and self development. An individual has to take it upon themselves partially to progress towards bettering themselves. Coders can’t rely on employers to teach them everything.

From the blog CS@Worcester – Kyle Polewaczyk by kpolewaczyk and used with permission of the author. All other rights reserved by the author.

Sprint 4: Reflections on Learning & Work Products

Sprint 4 of the semester got cut a little short because of spring break.  While I was in Cancun I can honestly say I was not too focused on the project.  Before the break, we were assigned our first issue, but none of us were able to reproduce the bug.  A few of my team members reached out to the AMPATH developers and we were able to get assigned a new issue.  We actually all had to take a step back and re-fork our whole project due to it being out of date.  When I did that, something got messed up because I currently cannot get the test server to go online.  I plan to get my personal issue resolved with the server within a few days.  Our new issue seems pretty simple and straight forward.  I look forward to working with my team to start fixing more and more actual issues with the system.  Hopefully this sprint will be much more productive because we will have a full sprint with no interruptions.

From the blog CS@Worcester – Alex's Comp Sci Blog by alexsblog13 and used with permission of the author. All other rights reserved by the author.

The Software Craftsman: Chapters 3 & 4

Chapter 3 of The Software Craftsman started off by discussing what exactly software craftsmanship is.  It gave the definition of software craftsmanship from a view different points of views such as; wikipedia, the authors personal definition, and a shorter more clean cut definition.  The chapter talked about how it is all about being professional when developing software which is something we have already previously learned in this class.  An interesting thing that this chapter discussed that I haven’t seen too much in previous chapters of this book or even in the whole Clean Coder book, was the history.  It gave in-depth information of the software craftsmanship movement and all the history you could possibly know behind it.  It was interesting to me to learn about historical details on where exactly this idea of software craftsmanship stemmed from.  Finally, the chapter covered the software craftsmanship manifesto.  The manifesto consisted of 4 major points:

  1. Not only working software, but also well-crafted software.
  2. Not only responding to change, but also steadily adding value.
  3. Not only individuals and interactions, but also a community of professionals.
  4. Not only customer collaboration, but also productive partnerships.

My favorite of the four was, number 1, “Not only working software, but also well-crafted software”.  This a very important point that every software developer needs to be aware of.  Just because a program may work, doesn’t mean it is crafted the way it should be.

Chapter 4  was about the attitude that a software craftsman should always have.  The chapter went through and mainly gave tips on how to improve yourself as a software craftsman.  Some of the advice that I personally took a lot from is always keeping our self up to date, practicing and balancing your work and personal life.  The topics of keeping yourself up to date and practicing are two things that I have seen a lot throughout this course.  It is clear that these two things are extremely important to any professional, but especially one dealing with technology.  Technology is advancing everyday and it is each individuals responsibility to keep up with it throughout their career.  Work-life balance is something that nearly everyone has to deal with at some point.  It is crucial for me as a soon-to-be software developer to start practicing different techniques to find the best work-life balance that works for me.  This chapter mentions a technique called the Pomodoro Technique.  This technique basically says that you should separate your work into 25 minute intervals.  It is proven that working in small intervals can maximize your creativity.  I am willing to give this technique a shot, even though I am not too confident it will work well for me.  I tend to be able to focus for a long period of time when I get into a groove.  If I was forced to stop myself when 25 minutes is up, it may set me back.  However, it can’t hurt to try.  Who knows I may find out that this is perfect for me.

From the blog CS@Worcester – Alex's Comp Sci Blog by alexsblog13 and used with permission of the author. All other rights reserved by the author.