Scrum agile project management
Many Scrum teams make the mistake of using the Sprint Review meeting for feedback from the Product Owner to the development team. Then the Sprint Review becomes a kind of ‘acceptance’ event. The Sprint Review meeting is, however, not intended for acceptance by the Product Owner.
Philippe Kruchten presents some ongoing research. It is about backlog and time-box, about value versus cost, about visible features versus invisible features (and in particular software architecture), about defects and technical debt, and more generally about release planning and sprint planning for non-trivial and long-lived software development projects.
Alastair Cockburn defines an information radiator “displays information in a place where passersby can see it.” There are many forms of information radiators in Agile and Scrum: sprint planning boards, product planning boards, road maps, …..
There are a lot of benefits with having the testers in the Scrum teams working side by side with the developers, and not in a separate test team. However, there are also some negative aspects that can endanger the quality of the work the testers are doing.
Agile coaches from BigVisible debate the pros and cons of using estimating tools for agile and scrum project planning.
“Self-organizing team” may be the most over-used, mis-understood, vague, and mis-leading phrase of the decade. So what is a self-organizing team? How are self-organizing teams different from other teams? How can managers and team members get the self-organizing mojo going? What are the challenges that self-organizing teams face? In this …
