This post originated from an RSS feed registered with Agile Buzz
by Franco Martinig.
Original Post: Technical Dependency Communication in Scaling Agile
Feed Title: Scrum Expert
Feed URL: http://feeds.feedburner.com/ScrumExpert
Feed Description: Resources, News and Tools for the ScrumMasters, Product Owners and Agile Developers
Developing large software systems automatically generate some technical dependency issues. If this is often managed by software architects in traditional projects, how do you communicate this technical dependencies when you are organized using an Agile approach? This is the topic discussed in the paper written by a Swedish research group. As Agile approaches are increasingly adopted by large software development organizations with distributed teams, the Agile breakdown of complex tasks create large challenges due to the technical dependencies between teams. This is not new, but with Agile the technical dependencies do not become more or less, they just become more obvious and this is actually a possibility for practice to deal with them. The research paper tried to answer two main questions based on a case study: * What are the challenges associated with technical dependencies between teams in a large-scale agile software development? * What affects the likelihood of a challenge to occur? The following technical dependencies are considered: * Unpredictability: teams find difficult to know beforehand what changes, issues, surprises, failures and successes they will come across during the development of a feature. * Conflicting priorities: a team might depend on a component that has lower priority in the backlog of another team. * Difficulty to understand overlapping and short release cycles when teams are constantly changing priorities in each sprint To mitigate the challenges created by these technical dependencies, the authors wrote that “one has to start with mitigating one challenge and then continue to exploit the [...]
Previous Topic
