The retrospective is one of 12 principles outlined in the Agile Manifesto. If this is easy to do this for collocated Scrum teams, how can you achieve good results if you have remote members. In this blog post, Robert Matheson provides a valuable collaborative retrospective technique that can be used for distributed Scrum teams.
Blogs on Scrum and Agile Project Management
Scaling and implementing an Agile approach in large projects is one of the hot topic in the Agile community, a natural consequences of the adoption of Agile by larger corporation. In this blog post, Ritika Nanwani shares some of her observations as a member of a large Scrum project.
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.
Managing the product backlog and prioritizing the user stories if one of the main responsibilities of the product owners in Scrum. In this blog post, Andy Carmichael explains how to assess the priority of product backlog items using the cost of delay.
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.
The product owner is one of the three roles of the Scrum framework for Agile project management. The product owner is responsible for defining and prioritizing the backlog and to convey the product vision to the Scrum team. Some people have compared this role to the traditional product manager position, but the context is different.In her blog post, Ellen Gottesdiener shares nine things that every product manager should know about being an Agile product owner.
Improvement is one of the core principle of the Agile Manifesto that states “At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly”. Retrospectives are a powerful technique to achieve this goal in Scrum and in this blog post, Jonathan Berger proposes seven practices to facilitate retrospectives.