Facing issue in managing workarounds in an IT development project

Challenge:

While developing a new software from scratch, many workarounds has to be identified, analysed  and then implemented. We were a team of 10 people amongst which 6 were developers and 4 were  testers. We were supported by our product owner in independent identification of the modules and  hence creating tickets for each and every task. Everything was working fine till 2-3 weeks, but soon  after we were in complete chaos. With significant number of tickets, it was very difficult to track the  tickets and identify who was working on a particular ticket and the work status of each tickets.  Hence, it significantly affected our team work as no one was apprised of the tasks other then their  own and hence created a lot of fuss in case tasks were inter dependent.

Selection:

As a team we came up with a solution that if there was a central system were all the tickets were  displayed visually, everyone would be apprised of the status of tickets of the whole team and  everyone would know who is working on which ticket and hence would plan their ticket accordingly.

Hence, we adopted the idea of “Visualisation”.

Application:

We incorporated a system of Kanban board, where each ticket is segmented into one of the 6 phases  namely: Prioritised, Analysis, Development, Peer Review, Testing, Accepted

Prioritised: This column contains all the tickets which needs to be worked on in current sprint.

Analysis: This column contains all tickets which has been picked up from prioritised column and  analysis is in progress.

Development: This column contains the tickets for which analysis is completed and development is I  progress.

Peer review:  This column contains tickets for which development is completed and peer review is in  progress.

Testing:  This column contains tickets for which development and peer review is completed and are  in testing phase.

Accepted: This column contains all the tickets for which all the work is completed and is in  acceptance phase.

Insight:

The Kanban model described above looks something like this:

Hence, with this pictorial description anyone can identify which phase the ticket is in currently and  plan their tickets accordingly in case of dependency. This improved overall monitoring of tickets.

Approach:

For the mentioned problem statement, I would stick to the “Visualisation” concept as it gives a clear  understanding of the tickets status and helps in overall monitoring of tickets.


Facing issue in managing workarounds in an IT development project Challenge : While developing a new software from scratch , many workarounds has to be identified , analysed and then implemented . We were a team of 10 people amongst which 6 were developers and 4 were testers . We were supported by our product owner in independent identification of the modules and hence creating tickets for each and every task . Everything was working fine till 2 - 3 weeks , but soon after we were in complete chaos . With significant number of tickets , it was very difficult to track the tickets and identify who was working on a particular ticket and the work status of each tickets . Hence , it significantly affected our team work as no one was apprised of the tasks other then their own and hence created a lot of fuss in case tasks were inter dependent . Selection : As a team we came up with a solution that if there was a central system were all the tickets were displayed visually , everyone would be apprised of the status of tickets of the whole team and everyone would know who is working on which ticket and hence would plan their ticket accordingly . Hence , we adopted the idea of “ Visualisation ” . Application : We incorporated a system of Kanban board , where each ticket is segmented into one of the 6 phases namely : Prioritised , Analysis , Development , Peer Review , Testing , Accepted Prioritised : This column contains all the tickets which needs to be worked on in current sprint . Analysis : This column contains all tickets which has been picked up from prioritised column and analysis is in progress . Development : This column contains the tickets for which analysis is completed and development is I progress . Peer review : This column contains tickets for which development is completed and peer review is in progress . Testing : This column contains tickets for which development and peer review is completed and are in testing phase . Accepted : This column contains all the tickets for which all the work is completed and is in acceptance phase . Insight : The Kanban model described above looks something like this : Hence , with this pictorial description anyone can identify which phase the ticket is in currently and plan their tickets accordingly in case of dependency . This improved overall monitoring of tickets . Approach : For the mentioned problem statement , I would stick to the “ Visualisation ” concept as it gives a clear understanding of the tickets status and helps in overall monitoring of tickets .