Issues, communication, and repositories

   Communication is key when working in groups or projects. At times members might go into a "ghost" mode where they are no available. Damon Poole states

"Developers often put off checking in ... But this leads to other problems such as losing work..."

   Today are going to look at a good method for communication regarding issues (or enhancements) for a project. Within our bitBucket/github project repository page there will be an "Issue" page, were we can raise flags for other team members to take a look at.

*Note that in the above posting, I'm able to select which team member needs to be alerted about the issue (perhaps if its their domain of the project), as well as alert them about the priority of the issue.

   Posting Issues is very straight forward and team members are even able to vote for issues that come up in regard to how to address them, which is very helpful when the team is larger than 2-3 members. By maintaining a check on the issues that are brought up during the scrum period, it allows for a quick response to keep the tasks rolling, and active communication through out the team. Which in the end will allow for the team to work in a manor that fosters their ability to work with velocity.

References:
 Atlassian Documentation. (n.d.). Retrieved September 28, 2015, from https://confluence.atlassian.com/bitbucket/use-the-issue-tracker-221449750.html Poole, D. (2005, July 25).
Do It Yourself Agile. Retrieved September 28, 2015, from http://damonpoole.blogspot.com/2005/07/check-in-early-and-check-in-often.html