If your application is not progressing as expected and it’s taking more time and budget to develop it and get it to market, then you may be suffering from “Single Project + Several Teams” collaboration issues.
In this blog we´ll explore some good practices that will help solve some of these issues.
Typically we see difficulties emerge when different teams responsible for different parts of the project need to work collaboratively together for the best results. For example, consider the following scenarios:
When several teams work together towards one common goal, numerous challenges emerge. In particular these challenges emerge because:
More helpful techniques are technical, grooming and business impact meetings. These meetings are not included in the general Scrum process (although sometimes grooming or backlog refinement occurs in Scrum), but they allow the Technical Leads/POs from different teams to join together and define the roadmap for the project.
Here the critical project flows need to be discussed and defined, based on prepared questions, defining alternate flows that could happen, and also gathering that information in a tool shared with all stakeholders.
The most important part of this collaboration is to define the shared goals:
Software development projects are challenging and even more so when they involve several teams which need to be collaborative and goal focused. There’s no simple solution for this, but applying the best practices outlined in this blog will increase the chances of success.
Finding the right balance between getting teams working together, motivated, and coordinated, while meeting time and budget constraints is crucial for achieving success in software development.
October 10 / 2019
October 03 / 2019
November 19 / 2014
In light of some of the major changes occurring at the moment within Microsoft, the forthcoming release of Visual Studio 2015, along with .NET 2015, promises to be particularly...Read post