Content tagged with: team
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.
Agile and Scrum project teams can adopt many different structures. In her blog post, Elizabeth Harrin gives a good summary of five structures that could be used by Agile teams based on a presentation made by Catherine Powell at the Oredev conference.
Collaborative risk management brings many benefits to Scrum teams, notably by generating wiser decisions and creating a collective ownership of issues. In his blog, Mike Griffiths describes some collaborative games that can be use project risk management.
Martin Alaimo thinks that personal issues are rarely discussed in Scrum retrospectives. In this article, he discusses how he includes in retrospectives a special section to address personal issues. He explains how he uses retrospectives to build Scrum between the Scrum team members.
In Agile and Scrum, we spend a lot of time talking about how to better manage software development teams using processes, methods, prescriptions and other rules of thumb. We spend very little time talking about the largest and most important ingredient of any agile team: the team and people themselves
Just imagine that you come to a different country and get a team of consultants with whom you need to do their first Scrum implementation project. On top of that, you are not managing the communication with the client, as you are only a sub-contractor. Not enough? You don’t speak official project language, which makes communication with the client VERY difficult. Want to know how it goes so far?