Software Development Capstone – Sprint 2 Retrospective

This past sprint was, to me, significantly less eventful than the first, but still very important in the progress of our capstone project. Over the past couple of weeks, I spent a lot of time focusing more on preparing for this upcoming Sprint 3, familiarizing myself with the tools and technologies that we will be using for our AMPATH project. We just received word about the kind of specific development work that we will be doing for the project, so keep an eye out for my Sprint 3 Retrospective for more information on that!

As I mentioned, Sprint 2 ended up being less productive for me, for a few reasons. We had a couple of class sessions cancelled (snow and other outside circumstances). While this fortunately did not slow our progress (everyone on our team has the AMPATH project built and running successfully!), our team has been taking advantage of each period of class time to discuss our progress, help each other out with any issues what we may be having, and planning our next courses of action. So, missing a couple of the sessions definitely slowed down some of the work that I could’ve been doing.

Another reason why this sprint has been a bit quiet is that we have not heard much about development ideas from the AMPATH team until yesterday, the final day of Sprint 2 and the beginning of Sprint 3. I’m very excited to start coding more, now that we have more of a plan, which involves mobile app development!

Our team had 2 tasks to complete this sprint – reading about Angular testing, and building and running the AMPATH project. Because I completed the second task during the previous sprint, I only had to concern myself with Angular unit testing, along with working together with my teammates to make sure that everyone could run the AMPATH project.

At the beginning of the first sprint, we had been tasked to learn about Karma and Protractor, two popular Angular unit testing tools. I, like other classmates working on development for the AMPATH project, utilized documentation for each tool in order to better understand how they work. My resource to understand Karma is found here, and for Protractor I used this source. Angular automatically incorporates Karma testing when creating any new project, so I spent more time reading about that tool. Karma and Protractor are similar, though, in that both load up servers on one or more browsers (specified when configuring) and runs the developed source code with the written tests. Then, the developer is notified whether each test passes or fails, via command line or through the browser.

This sprint really made me appreciate the quality assurance testing course that I took last semester. Learning about Java unit testing and its basic framework made the comprehension of this newer concept a bit easier.

Once again, I’m looking forward to posting more about progress that our team makes during this upcoming sprint! We have a lot of exciting ideas to discuss and potentially work with.

Thanks for reading!

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this:
search previous next tag category expand menu location phone mail time cart zoom edit close