Articles tagged with: team
For best results from Agile, you need a solid team. If you belong to, manage, or lead an Agile team, you’ve probably seen that process alone doesn’t translate to great results – and that having a cross-functional group of 7 +/- 2 “resources” doesn’t either. Instead, what makes Agile come to life is the team’s motivated, engaged individuals who communicate, collaborate, and respond effectively. In …
The first value of the Agile Manifesto is to prefer “Individuals and interactions over processes and tools”. But how can you know if your individuals and your teams like your current Agile approach. In his article, Henrik Kniberg present a simple tool to assess the health of your Scrum teams.
In large Agile projects where a Scrum team cannot deliver the full system, you have different options to organize your team. You can use feature teams that work on a set of user stories or component teams that work on a subsystem or component. In his blog post, Michael Valenta reports his experience as a ScrumMaster from the usage of features teams.
Some companies such as HubSpot or Google have developed techniques that allow small teams to create, test and deploy a continuous stream of releases. These companies are able to harness highly distributed Agile teams and scale to very large projects, while avoiding the tyranny of long meetings, conference calls, detailed estimates and sticky notes.
It’s very easy to become hierarchical and turn into a “bank” when software company is growing fast. Is there a way to avoid that? How to keep the focus on value creation? What about Value departments, not Functional departments? This presentation shares ideas what we can learn from Scrum and apply in organizational design. It shares hypothesis how a company could look like when everybody …
When companies transition to Agile, it is not too difficult to find new roles for member of the current software development teams. Finding a place for middle management in the new organization is not so easy and some people even advocates to get rid of them. In this blog post, Em Campbell-Pretty brings her own middle management perspective to this discussion.
One of the technical practices of Agile software development is to support cross-functional teams where members perform multiple activities like requirements, coding and testing. In their book “Being Agile”, Leslie Ekas and Scott Will discusses the difficulties of creating a whole team.
As Agile project management is being widely adopted, the questions of if and how it could scale is a main topic of discussion. In this blog post, Gilt explain how it scales Agile with teams, ingredients, initiatives and KPIs.
Patterns are the new defacto Scrum standard. In recent years, international Scrum Leadership has been meeting about once a year to write a rationalized foundation for Scrum using Organizational Patterns as a public resource.
If you are following an Agile approach to project management like Scrum, you should have adopted a continuous improvement practice. Retrospectives are the name of the meeting when the Scrum team makes a pause to think on how to improve its current. Fun Retrospectives is a book that should help you to animate these meetings.