Content tagged with: team
In this article, Craig Larman and Ahmad Fahmy discuss how long does it take an organization to reorganize in order to adopt Scrum. This article is based on the transition done at Bank of America’s Merrill Lynch Global Securities Operations Technology where the software development teams went from a traditional activity based organisation (business analysts, developers, …) to Scrum.
The Scrum approach recommends to deliver software incrementally in small iterations. This seems to be always an issue with activities that require a global view on the developed application like the software architecture or the user interface. In this blog post, Aviva Rosenstein, who manages user research for Salesforce, shares here experience about integrating user experience (UX) design into the Scrum development process.
Scrum requires that members of the team collaborate. One of the agile software development practice used to collaborate is pair programming. In his blog post, Erik Brickarp reports his experience when pairing a programmer and a software tester.
«Self-organizing team» may be the most overused, misunderstood, vague, and mis-leading phrase of the decade. What is a self-organizing team? How are self-organizing teams different from other teams? What makes self-organizing teams the key to unlocking creativity and agility? This talk explores the elements of success for self-organizing teams, and show why such teams are essential for meeting the demands of a fast-changing world.
If you put mayonaise in your cake because you don’t have butter, you aren’t being pragmatic, you’re being disgusting. I don’t care how good your experience is with the mayonaise in other recipes. I don’t care about it’s quality. It just doesn’t work in cake. The same goes for putting project managers and software architects in Scrum teams.
Agile software development challenges traditional project management approaches with self-organizing teams where individual members have more influences on the project success. How do you hire Scrum team member in this type of context. Mitch Lacey proposes to adopt the immersive interviewing technique to hire for agile software development teams. And like all good agile practices, it begins and ends with the team.
It’s fairly hard to know what solid testing is all about within Agile and Scrum teams. What traditional practices are fine to continue, which ones need modification and what totally new approaches are necessary. Moving from traditional to agile testing is often a high-wire balancing act to some degree with no clear direction.
We know that self-organization is a critical aspect of every successful Agile and Scrum team and we also know that it takes trust, respect, openness and responsibility; so why many teams have a hard time to achieve it?
Collaboration Games from the Growing Agile Toolbox is a free e-book written by Karen Greaves and Samantha Laing that proposes ten games to build collaboration in Agile teams.
Absent ScrumMaster, poorly defined requirements, inexperienced team, absent product owner, impossible goals. Sometimes things can go wrong even in projects that use an Agile approach like Scrum. The main issues are absent product owner or ScrumMaster, an inexperienced team, poorly defined requirements or impossible goals. In this article, Avelino Ferreira Gomes Filho shares some of his experience as a replacing ScrumMaster in troublesome Scrum projects.