Browse Prior Art Database

Cognitive Agile Backlog Grooming Engine Disclosure Number: IPCOM000248159D
Publication Date: 2016-Nov-02
Document File: 8 page(s) / 99K

Publishing Venue

The Prior Art Database


"Cognitive Agile Backlog Grooming Engine" is a solution that will completely change the way "Agile Backlog Planning" is done. With cognition built into the solution, a lot of repeatable processes and artifacts can be prescribed to the team through pre-defined templates, which can then be used by the team to only work on customizing the delta, thereby reducing overhead effort by at least 50%. This solution also addresses potential risks that may arise from lack of full time SME involvement.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 25% of the total text.

Page 01 of 8

Cognitive Agile Backlog Grooming Engine

1. Background :

In today's world of software development, a lot is emphasized on Agility. A very important aspect of an Agile team is their ability to continuously plan. The challenge with this is that the entire team may not be available together all the time - like during the initial stages where the team is still being setup. Unless the team is experienced and mature to a level where they can make-up for this without hurting the schedules, these ceremonies become a bottleneck. Moreover, due to cost implications the team's overall experience is also reducing. This makes it even more important for the Scrum Masters to find an even ground so that both cost and time are taken into consideration while not ignoring the Agile principles. This can be done by allowing repeatable items to be more prescriptive.

The new age delivery model as in the example of any "as a Service" offerings on the Cloud is such that, there is a need for quick turn-around of finished products into the market. The clients are looking for solutions that can be built in a few months, delivering working software incrementally, and this is where some of the pre-built Offerings come into play. Since a lot of historical data that can be used to automate most of the processes are not being used the right way, there is a big opportunity now to use it and reduce a lot of overhead process.

The solution to this problem cannot be skipping these ceremonies. They are as important (if not more) as any of the review or retrospective meetings. So one of the solution is to help the team do most of the administrative tasks that is done in these planning sessions, thereby letting the team concentrate on their tasks on hand. This will reduce the time consumed by these planning ceremonies by at least 50-60%.

2. Summary :

We present a Method and Framework for Cognitively performing Agile Planning activities through the Agile Tracking and Planning tools.

Today's projects are getting more and more offering driven with significant asset / IP packaged with prescriptive approaches to improve efficiencies. Agile tracking and planning tools can be used to create such offering templates. Product Backlog Items (Epics, Stories, Tasks, Defects, etc.) across these projects that belong to a particular offering will be at least 60% reusable. So these templates will have most of the reusable items pre-populated. Fields like Story Points, Business Value Points, and Technical Value Points will be used. Based on the combination of historical data and current data, the tool will be able to automatically determine the Sprint Backlog (using the average velocity, story points, business value points and technical value points). With the help of data analytics, we should be able to help teams automatically do all that they would do in a typical planning session - which includes grooming stories into tasks, estimating each of them, and prioritizing.

Collaborative plan...