Home » Archives

Content tagged with: team

[12 Dec 2012 | No Comment | ]

In this article, Henrik Kniberg and Anders Ivarsson present the story of scaling Agile at Spotify with over 30 teams across 3 cities. They describe the current organization at Spotify. The Squads are similar to Scrum teams. They are self-organizing teams and some use Scrum but other use Kanban or mixed approaches.

[10 Dec 2012 | 2 Comments | ]

Self-organizing Scrum and agile teams need to determine how best to manage the flow of their work to get the job done each iteration. Flexible and high-performing agile development teams are composed of members with T-shaped skills and a Musketeer attitude that enable them to swarm to success.

[3 Dec 2012 | One Comment | ]

As Agile and Scrum are increasingly used to manage software development projects in large companies, Nancy Nee, VP Global Product Strategy at ESI International, provides us with her viewpoint on how the transition to Agile is going on. She also shares some advice on how make the adoption process as smooth as possible.

[21 Nov 2012 | No Comment | ]

In this blog post, J.D. Meier shares his experience of leading high-performance distributed teams for more than ten years at Microsoft. He describes a weekly schedule that begins with identifying 3 wins for the week on Monday to discussing 3 things going well and 3 things to improve on Friday.

[8 Oct 2012 | No Comment | ]

This article from Rob Maher focuses on how to increase productivity. It discusses how changing a project staffing model could increase the productivity of project teams (PDF document). There is published evidence that short-lived groups of people brought together for a project are correlated with lower productivity. His view is that in an agile world, teams are permanent and the organization optimizes at the team level. Permanent teams enable consistent estimation, which is not possible using the matrix approach.

[4 Oct 2012 | No Comment | ]

Scrum teams usually develop iteratively new product features. In larger project, teams can also be organized around layers or components of the product. In this article, Mukesh Chaudhary discusses how to manage the complexity with Scrum component teams and integration of their deliverables to make up a feature.

[12 Sep 2012 | No Comment | ]

Large organizations are using balanced scorecards and dashboards to measure, monitor and forecast the performance of the organization and connect those to its vision, goals and objectives. Metrics is important for management, but how do you design metrics for agile teams? How will the metrics affect the behavior of the teams? In this seminar, you will get an insight into different types of agile metrics that preserves and promotes collaboration of agile development teams.

[11 Sep 2012 | No Comment | ]

In this article, Steve Hunton explains that, even if people expect that the shift to Agile practices includes a wholesale shift of roles,, the ScrumMaster does not play the part of the traditional project manager. He thinks that the project manager role is more filled by the product owner. The project manager is a decision maker accountable to the business for accomplishing the project objectives. The ScrumMaster is a coach and facilitator that sits between the project and the customer. He isn’t responsible for the project or managing the development …

[5 Sep 2012 | No Comment | ]

The early agile literature was adamant about two things: stick with small teams and put everyone in one room. However, in the years since the Agile Manifesto, the increasing popularity of agile and the dramatic improvements it brings has pushed it onto larger and larger projects. Additionally, having an entire team, especially on a large project, in one room, or even one building is a luxury no longer enjoyed by many projects.

[29 Aug 2012 | No Comment | ]

Learn how to achieve multiple team collaboration in large scale software development projects. Self-organization is a key concept for all Lean-Agile methods. However, as projects expand across the enterprise and, more specifically, cut across multiple teams, teams clearly can’t just organize in any way they want to. A blend of top-down direction with bottom-up self organization is needed. Lean provides the insights necessary for teams to self-organize within the context of the value stream within which the teams work. A top-down perspective, created by driving from business value, can …