Bug Tracking

 A bug is an error in a product’s code which stops the working of a developed software therefore making it vital to detect a bug before the final product is made available for customers. Software development teams always associate bug tracking with testing and most techniques of software creation have special steps of test conduction such as the Traditional waterfall methodology. There exist methodologies with flexible testing and tracking approaches like the agile methods that encourage constant tracking during project realization. The bugs are usually tracked with the aid of a special software thereby making developing easier. Bug tracking systems are the applications that aid in detecting bugs, reporting on them, and creating lists of bugs for fixing. This paper therefore discusses the Pivotal tracker software in terms of its bug tracking process for my proposed project, to facilitate the knowing the voting status of all people process using android devices.

Software description

Pivotal Tracker was developed in laboratories in 2006 to ease and facilitate development processes and team collaboration because it monitors progress throughout the project making teams that use agile methodologies in software development benefit as they are to list down actionable items, prioritize tasks, assign given activities, and set their deadlines. It is therefore an opinionated and cloud-based project management tool that backs bug tracking as a project management process as it will bring on board all team members despite the distribution, into the same virtual room. The tracker will work by automatically calculating the estimated time required to finish the voting, and calculate their voting status by locating them everywhere they are globally.

The users

This therefore allows managers, more so those responsible for voting processes to have better delivery estimates of the voting status depending on real time circumstances and the workforce. This solution will give a guided iteration planning tool that will enable the users to prioritize on project tasks as well as break them down into manageable chunks. Pivotal android mobile tracker will allow the team members to know exactly what happens at given times during voting processes thereby making creation and responding to tasks easy. This tracker will aid in the management of our project’s mobile phone app thus facilitating its realization, and efficiency in voting.

Bugs vs feature request

The tracker will organize all stories into story types that include bug, feature, chore and release and all of then use the same obligatory workflow of icebox, backlog, current and done. It will give great visibility to the status of one’s bugs and the overall project via personal work spaces and strong charts and reports. For my project, each developer will be able to see all stories that are assigned to them in a single space and this will help ensure nothing escapes through cracks. This type of detailed reporting will allow Kevin Hill as the project manager to constantly supervise the progress and speed of the project thus identify issues as they occur.

System monitoring

With this tracker, the customer, project manager (Kevin Hill) or the product owner (Charles Lee Ray) will be adding new feature stories as the commencement of the process. This will be done in cooperation with other team members for instance story mapping, specifications, workshops as well as an iteration planning meeting. At this step mock-ups and assets are allowed for inclusion in the story and stories are in an unscheduled state; icebox, unestimated and have points approximate in place of an action button. They will then be prioritized by the customer/ PM/ PO in a backlog leaving them in an unstarted state as they remain unestimated. The customer/PM/PO will then prioritize stories in Backlog; the stories will then be in the unstarted state, and will remain unestimated. They will be estimated by the team while discussing each story so as to attain a mutual understanding followed by the addition of extra data followed by collective estimation.

At this point the stories have a start button and they are started; the developers (Jason Vorhees and Freddy Kreuger) will then click on the start button on the following unstarted estimated story in the present iteration. If the story turns out to be a feature that has yet to be estimated, the developer will be impelled to allocate a point value before continuing making the story to be in a started state with a finish button. Unless it has been preassigned, the individual who clicked on start becomes the story owner. The developers will collaborate with other team members to carry out testing and coding in turn building feature increment represented by the story. Upon passing the coding and testing activities, the developers will click on finish thus displaying the Deliver button. This mobile app will also have the ability to send and receive texts, and to locate anyone everywhere.

Follow up with the requester

After building the CI-newly built committed code passed, it will then be deployed to testing and the stories marked as delivered by a team member making the Green accept and red Reject buttons visible. The Customer/PM/PO together with testers, designers and other team members will verify if all set criteria have been adhered to and either accepts or rejects the story thus completing the feedback loop. Accepted stories at this point will turn green and move to the top of the current iteration then move to the Done panel at the end of the iteration.

Bugs on the other hand possess a similar work flow as feature stories and can be tagged with labels that relate them to a specific release, feature area of a given epic. In my case the product owner Charles Lee Ray will prioritize them as a story in the backlog and label it as “needs design” for placing the teams design in line to be reviewed for the results that came up;  Afterwards the designer will then add mock ups and remove the label. Kevin Hill will then meet with the designer, Jackson Nicholson and the programmer for a discovery workshop three days prior to the IPM to talk over the story while using an example in order to come up with the  desired behaviors, establishing rules for the story then jotting any oexceptional queries.

Assign unique code

The whole team will meet with the IPM and go over the rules with Kevin Hill. The team will go in depth on the topic of dependency for the server side of story along with the different options for implementation. Afterwards they’ll be able to provide an estimate to the story on three three points; lastly Kevin Hill will add a blocker to it. Blocking will be accepted and should automatically resolve the issue, next time the story itself. Jason Vorhees and Freddy Kreuger will start it up, while assigning themselves as the story’s owner. The code will then be tested. Next , they will go over what was , then and only then discuss them with Jackson and Hill in case new questions may/may not come about.

Once the code passes, samples will be automated throughout the  test environment and Jackson will verify and click on the Deliver button. Jackson will then have to validate how the  search’s turned out and felt while accepting it after which more explanatory testing is done to determine issues outside the story’s scope followed by adding of more stories. Jackson and Hill will then accept the story. An issue reported as a bug will be a missing feature or any behavior plus with this story being changed from a bug then towards to a the main event or it will be labeled with a tag that states “ its not a bug” ; then the status will be changed to to being accepted. Some bugs may linger long enough to be fixed by different stories and a good option here will be to comment on anything that was tried on it as “non-reproducible” then change the state to “Accepted”.


The necessary steps and processes required for the implementation of this project have been explained in details. Bug tracking is the final stage of projects realization but in some instances testing and bug detection may cause trouble considering it is hectic to fix a problem when the final product is almost ready. It is therefore expected that this project will run smoothly and that the expected objectives will be achieved. This will enable the project team to eventually identify, fix, and log the bugs when undertaking various tasks.