How a Bank’s IT Teams Used AI to Organise Software Planning

The Challenge

A bank’s IT and software teams dealt with a fast-growing volume of tasks, needs and technical records. Software teams, project managers, product managers and technical leads all needed to turn this material into work they could plan, prioritise and track.

As the number of items grew, keeping the overall picture clear became harder. A single need or issue could hold several separate pieces of work, and understanding it meant reading through the full record first. Teams lost time in planning and follow-up, the backlog was harder to see clearly, and coordination between teams and technical discussions were less productive than they could have been.

The Solution

With cognipeer Studio, our team configured an AI planning assistant for the bank’s software and project work. Team members shared a need, an issue or a technical record with the assistant, which summarised the content and broke it down into separate work items. Instead of starting from a long description, the team could see the individual pieces of work it contained.

The assistant then presented these items in a more organised view for prioritisation and follow-up. For requests that called for it, the assistant also helped the team understand which technical areas a request was likely to affect, giving technical leads and software teams a clearer basis for discussion. Project managers, product managers and technical leads kept ownership of priorities and plans, using the assistant’s output to support their own decisions.

Implementation

1. Started with shared records. We set up the assistant to work with the needs, issues and technical records that team members shared with it.
2. Configured summaries and work items. The assistant summarised each input and separated it into distinct work items.
3. Organised the planning view. Work items were presented in a consistent view that supported prioritisation and follow-up.
4. Added technical impact support. Where needed, the assistant pointed out the technical areas a request might affect, with decisions remaining with the team.

Business Impact

Planning started from a clearer picture. Requests and technical records reached the planning process already summarised and broken into work items, so teams spent less time unpicking them and more time deciding what to do next. With the same organised view available to everyone involved, coordination between teams improved and technical discussions could focus on the decisions at hand.

• Clearer backlog visibility across needs, issues and technical records.
• Faster planning, starting from summarised work items.
• Better coordination between teams working from the same organised view.
• More productive technical discussions, supported by a clearer view of the areas affected.

Technology Behind the Solution