Monthly Archives: March 2017

Week 5 Reflections

Well this time
around the sprint seems to be getting more comfortable as far as us
working as a team and getting things done as well as discussing what
needs to be done and who will be doing what and the likes. It has
been a rather uneventful sprint in my opinion as we did some waiting
on the folks at ampath to figure out what they wanted us to do and
came up with 4 issues in the Jira board for us. That was actually
pretty cool to see an issues board and to see how it operates as I am
sure that when I get a job in the field I will be using something
similar. We had a roll of for who would get what issue because our
team and another wanted to work on the same issue. We lost and got
our second choice, NGPOC-185 in which there is a concern over logging
out when you are in the middle of filling out a form it doesn’t
save the data you had in the form and they would like a modal to pop
up asking if you would like to save or not. I have been going over
ampath code as well as documentation(Angular) to learn about where
the issue is and how to implement a fix.

I gained some more
knowledge this time writing the login and auth modules. It was a bit
of my own and a bit of looking at the code when I needed to, bu I
feel more comfortable with Angular, not like super but confident I
can actually do stuff with it now. I have also been going through a
book on Angular 2 by Pablo Deelman called “Learning Angular 2”
courtesy of ACM. It is good book so far and basically covers
everything needed for Angular including testing. It should help me
gain more experience with the language.

There really isn’t
much more I can offer, but next sprint looks like it will keep us
fairly busy as we should have the issue solved and implemented and
apparently there is a list of other issues for us to tackle now so
things are starting to get rolling along. Until next time….

From the blog format c: /s by c-braley and used with permission of the author. All other rights reserved by the author.

Week 5 Reflections

Well this time
around the sprint seems to be getting more comfortable as far as us
working as a team and getting things done as well as discussing what
needs to be done and who will be doing what and the likes. It has
been a rather uneventful sprint in my opinion as we did some waiting
on the folks at ampath to figure out what they wanted us to do and
came up with 4 issues in the Jira board for us. That was actually
pretty cool to see an issues board and to see how it operates as I am
sure that when I get a job in the field I will be using something
similar. We had a roll of for who would get what issue because our
team and another wanted to work on the same issue. We lost and got
our second choice, NGPOC-185 in which there is a concern over logging
out when you are in the middle of filling out a form it doesn’t
save the data you had in the form and they would like a modal to pop
up asking if you would like to save or not. I have been going over
ampath code as well as documentation(Angular) to learn about where
the issue is and how to implement a fix.

I gained some more
knowledge this time writing the login and auth modules. It was a bit
of my own and a bit of looking at the code when I needed to, bu I
feel more comfortable with Angular, not like super but confident I
can actually do stuff with it now. I have also been going through a
book on Angular 2 by Pablo Deelman called “Learning Angular 2”
courtesy of ACM. It is good book so far and basically covers
everything needed for Angular including testing. It should help me
gain more experience with the language.

There really isn’t
much more I can offer, but next sprint looks like it will keep us
fairly busy as we should have the issue solved and implemented and
apparently there is a list of other issues for us to tackle now so
things are starting to get rolling along. Until next time….

From the blog format c: /s by c-braley and used with permission of the author. All other rights reserved by the author.

Week 5 Reflections

Well this time
around the sprint seems to be getting more comfortable as far as us
working as a team and getting things done as well as discussing what
needs to be done and who will be doing what and the likes. It has
been a rather uneventful sprint in my opinion as we did some waiting
on the folks at ampath to figure out what they wanted us to do and
came up with 4 issues in the Jira board for us. That was actually
pretty cool to see an issues board and to see how it operates as I am
sure that when I get a job in the field I will be using something
similar. We had a roll of for who would get what issue because our
team and another wanted to work on the same issue. We lost and got
our second choice, NGPOC-185 in which there is a concern over logging
out when you are in the middle of filling out a form it doesn’t
save the data you had in the form and they would like a modal to pop
up asking if you would like to save or not. I have been going over
ampath code as well as documentation(Angular) to learn about where
the issue is and how to implement a fix.

I gained some more
knowledge this time writing the login and auth modules. It was a bit
of my own and a bit of looking at the code when I needed to, bu I
feel more comfortable with Angular, not like super but confident I
can actually do stuff with it now. I have also been going through a
book on Angular 2 by Pablo Deelman called “Learning Angular 2”
courtesy of ACM. It is good book so far and basically covers
everything needed for Angular including testing. It should help me
gain more experience with the language.

There really isn’t
much more I can offer, but next sprint looks like it will keep us
fairly busy as we should have the issue solved and implemented and
apparently there is a list of other issues for us to tackle now so
things are starting to get rolling along. Until next time….

From the blog format c: /s by c-braley and used with permission of the author. All other rights reserved by the author.

Week 5 Reflections

Well this time
around the sprint seems to be getting more comfortable as far as us
working as a team and getting things done as well as discussing what
needs to be done and who will be doing what and the likes. It has
been a rather uneventful sprint in my opinion as we did some waiting
on the folks at ampath to figure out what they wanted us to do and
came up with 4 issues in the Jira board for us. That was actually
pretty cool to see an issues board and to see how it operates as I am
sure that when I get a job in the field I will be using something
similar. We had a roll of for who would get what issue because our
team and another wanted to work on the same issue. We lost and got
our second choice, NGPOC-185 in which there is a concern over logging
out when you are in the middle of filling out a form it doesn’t
save the data you had in the form and they would like a modal to pop
up asking if you would like to save or not. I have been going over
ampath code as well as documentation(Angular) to learn about where
the issue is and how to implement a fix.

I gained some more
knowledge this time writing the login and auth modules. It was a bit
of my own and a bit of looking at the code when I needed to, bu I
feel more comfortable with Angular, not like super but confident I
can actually do stuff with it now. I have also been going through a
book on Angular 2 by Pablo Deelman called “Learning Angular 2”
courtesy of ACM. It is good book so far and basically covers
everything needed for Angular including testing. It should help me
gain more experience with the language.

There really isn’t
much more I can offer, but next sprint looks like it will keep us
fairly busy as we should have the issue solved and implemented and
apparently there is a list of other issues for us to tackle now so
things are starting to get rolling along. Until next time….

From the blog format c: /s by c-braley and used with permission of the author. All other rights reserved by the author.

Week 5 Reflections

Well this time
around the sprint seems to be getting more comfortable as far as us
working as a team and getting things done as well as discussing what
needs to be done and who will be doing what and the likes. It has
been a rather uneventful sprint in my opinion as we did some waiting
on the folks at ampath to figure out what they wanted us to do and
came up with 4 issues in the Jira board for us. That was actually
pretty cool to see an issues board and to see how it operates as I am
sure that when I get a job in the field I will be using something
similar. We had a roll of for who would get what issue because our
team and another wanted to work on the same issue. We lost and got
our second choice, NGPOC-185 in which there is a concern over logging
out when you are in the middle of filling out a form it doesn’t
save the data you had in the form and they would like a modal to pop
up asking if you would like to save or not. I have been going over
ampath code as well as documentation(Angular) to learn about where
the issue is and how to implement a fix.

I gained some more
knowledge this time writing the login and auth modules. It was a bit
of my own and a bit of looking at the code when I needed to, bu I
feel more comfortable with Angular, not like super but confident I
can actually do stuff with it now. I have also been going through a
book on Angular 2 by Pablo Deelman called “Learning Angular 2”
courtesy of ACM. It is good book so far and basically covers
everything needed for Angular including testing. It should help me
gain more experience with the language.

There really isn’t
much more I can offer, but next sprint looks like it will keep us
fairly busy as we should have the issue solved and implemented and
apparently there is a list of other issues for us to tackle now so
things are starting to get rolling along. Until next time….

From the blog format c: /s by c-braley and used with permission of the author. All other rights reserved by the author.

Week 5 Reflections

Well this time
around the sprint seems to be getting more comfortable as far as us
working as a team and getting things done as well as discussing what
needs to be done and who will be doing what and the likes. It has
been a rather uneventful sprint in my opinion as we did some waiting
on the folks at ampath to figure out what they wanted us to do and
came up with 4 issues in the Jira board for us. That was actually
pretty cool to see an issues board and to see how it operates as I am
sure that when I get a job in the field I will be using something
similar. We had a roll of for who would get what issue because our
team and another wanted to work on the same issue. We lost and got
our second choice, NGPOC-185 in which there is a concern over logging
out when you are in the middle of filling out a form it doesn’t
save the data you had in the form and they would like a modal to pop
up asking if you would like to save or not. I have been going over
ampath code as well as documentation(Angular) to learn about where
the issue is and how to implement a fix.

I gained some more
knowledge this time writing the login and auth modules. It was a bit
of my own and a bit of looking at the code when I needed to, bu I
feel more comfortable with Angular, not like super but confident I
can actually do stuff with it now. I have also been going through a
book on Angular 2 by Pablo Deelman called “Learning Angular 2”
courtesy of ACM. It is good book so far and basically covers
everything needed for Angular including testing. It should help me
gain more experience with the language.

There really isn’t
much more I can offer, but next sprint looks like it will keep us
fairly busy as we should have the issue solved and implemented and
apparently there is a list of other issues for us to tackle now so
things are starting to get rolling along. Until next time….

From the blog format c: /s by c-braley and used with permission of the author. All other rights reserved by the author.

Week 5 Reflections

Well this time
around the sprint seems to be getting more comfortable as far as us
working as a team and getting things done as well as discussing what
needs to be done and who will be doing what and the likes. It has
been a rather uneventful sprint in my opinion as we did some waiting
on the folks at ampath to figure out what they wanted us to do and
came up with 4 issues in the Jira board for us. That was actually
pretty cool to see an issues board and to see how it operates as I am
sure that when I get a job in the field I will be using something
similar. We had a roll of for who would get what issue because our
team and another wanted to work on the same issue. We lost and got
our second choice, NGPOC-185 in which there is a concern over logging
out when you are in the middle of filling out a form it doesn’t
save the data you had in the form and they would like a modal to pop
up asking if you would like to save or not. I have been going over
ampath code as well as documentation(Angular) to learn about where
the issue is and how to implement a fix.

I gained some more
knowledge this time writing the login and auth modules. It was a bit
of my own and a bit of looking at the code when I needed to, bu I
feel more comfortable with Angular, not like super but confident I
can actually do stuff with it now. I have also been going through a
book on Angular 2 by Pablo Deelman called “Learning Angular 2”
courtesy of ACM. It is good book so far and basically covers
everything needed for Angular including testing. It should help me
gain more experience with the language.

There really isn’t
much more I can offer, but next sprint looks like it will keep us
fairly busy as we should have the issue solved and implemented and
apparently there is a list of other issues for us to tackle now so
things are starting to get rolling along. Until next time….

From the blog format c: /s by c-braley and used with permission of the author. All other rights reserved by the author.

Week 5 Reflections

Well this time around the sprint seems to be getting more comfortable as far as us working as a team and getting things done as well as discussing what needs to be done and who will be doing what and the likes. It has been a rather uneventful sprint in my opinion as we did some waiting on the folks at ampath to figure out what they wanted us to do and came up with 4 issues in the Jira board for us. That was actually pretty cool to see an issues board and to see how it operates as I am sure that when I get a job in the field I will be using something similar. We had a roll of for who would get what issue because our team and another wanted to work on the same issue. We lost and got our second choice, NGPOC-185 in which there is a concern over logging out when you are in the middle of filling out a form it doesn’t save the data you had in the form and they would like a modal to pop up asking if you would like to save or not. I have been going over ampath code as well as documentation(Angular) to learn about where the issue is and how to implement a fix.
I gained some more knowledge this time writing the login and auth modules. It was a bit of my own and a bit of looking at the code when I needed to, bu I feel more comfortable with Angular, not like super but confident I can actually do stuff with it now. I have also been going through a book on Angular 2 by Pablo Deelman called “Learning Angular 2” courtesy of ACM. It is good book so far and basically covers everything needed for Angular including testing. It should help me gain more experience with the language.

There really isn’t much more I can offer, but next sprint looks like it will keep us fairly busy as we should have the issue solved and implemented and apparently there is a list of other issues for us to tackle now so things are starting to get rolling along. Until next time….

From the blog format c: /s by c-braley and used with permission of the author. All other rights reserved by the author.

Sprint 3 Reflection

This sprint was the most productive so far. Each member of the team was given access to the AMPATH JIRA site. The AMPATH team uses JIRA to track issues and layout tasks than need to be completed. Now that we have access to the issue tracking system, a member of the AMPATH team picked a list of issues he though the class could handle. The issue we decided to tackle was not an issue with the code but a request by the users to move a button. The process of moving the button started off slow as we could not locate the button in question with in the system. This problem was further complicated by the fact that we could not load the forms on the site. After messaging our main contact at AMPATH we had an idea of what needed to be done but still were having issues locating the button. After some exploring we finally found the button. The button is to return to a form draft, this button is only visible if there is a form that has been open but not submitted. Our initial efforts to find the button were destine to be fruitless as we could not load any of the forms.
I believe the coming sprint will be the the first sprint where we can fully experience the Scrum process and see how the team works together. The past weeks have been good but with only smaller tasks it there was no sense of urgency. Now that we have an issue to work on team members will need to take responsibility of there individual part.

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

Sprint 3: Reflections on Learning & Work Products

This sprint was the most successful yet.  I think we are all starting to really get the hang of things in our group and daily scrum meetings each week.  We are now at the point where we have been assigned issues from AMPATH and are diving head first into the openMRS code.  My big obstacle this week was trying to figure out why it was saying I had the wrong login credentials for the AMPATH standalone server.  I realized half way through the sprint that I was stuck on the issue for too long, so I decided to go to my teammates for help.  In a few days, one of my team members actually found the solution to the issue.  All I had to do was switch my web browser to google chrome and download a plugin I was missing.  The lesson I am going to take from this sprint is to not spend too much time getting stuck on something without asking for help.  It is always a good idea to try and figure out a problem by yourself but if it’s coming to the point where it is taking you a little too much time, you should always ask for help.  This semester is pretty short, so I don’t want to waste any time that I could be focusing on something else.  This next sprint I plan to get more done then I did this sprint.  I am not completely satisfied with the amount of work I accomplished this sprint and wish to improve.

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.