This post includes the discussion around combining the roles of scrum master and product owner.
When developers are promoted into a position leading the team, a different skillset is needed. InfoQ interviewed Patrick Kua, author of the book, Talking with Tech Leads, about the need for technical leaders, differences between the Scrum master and Tech Lead roles, leadership skills and what technical leaders can do to support people in developing their skills and abilities.
Impediments are issues that hinder agile teams. They are problems that teams are facing, which they need to solve. Managers can help agile teams in several ways to solve impediments.
Bob Marshall explains the reason of failing of scrum master in most of the organizations as the lack of awareness on the part of adopting scrum and scrum master’s responsibility to tackle organizational dysfunction.
Random retrospective activity generator "Retr-O-Mat" now available as printed edition, contains 50 activities from various sources.
Agile retrospectives help teams to find and do actions to improve continuously. There are different ways to do follow up on the actions and to evaluate if actions are leading to better team performance and more value delivered to customers.
An agile checklist is a tool which can help you to assess your agile implementation in an organization, and assist when adopting agile. Some examples of lists with things that you can check when adopting agile.
A new "Scrum Kickoff Planner" has just been released by Adam Weisbart with the aim of facilitating team discussion around the important facets of starting a new Agile team or project.
The debate about the overlap between Scrum Master and Project Manager roles continues. Many commentators and bloggers strongly advise against combining the two roles, yet many role descriptions and job advertisements combine them into a single job.
The debate as to whether a ScrumMaster is a full-time or part-time role in an Agile teams has created a lot of discussion in the community in recent months. As a result, the community have developed a ScrumMaster Manifesto.
Tony Wong, a project management blackbelt, enumerates some practical points on individual procutivity. This article wonders how well these apply to software development and contrasts his list with that of other lists.
The CSM Certification from the Scrum Alliance is granted to individuals that participate in a two day certification course and complete a pass/pass (e.g. can’t be failed) test. The testing process will be changed in 2012 to include a pass/fail test, and a new Professional Development Unit (PDUs) program will be rolled out no later than January 2013 for CSM’s to maintain their certification.
This is the 4th quarter 2011 update of scrum extensions. InfoQ will be looking at proposed and approved extensions each quarter to see how scrum changes and evolves.
Ken Schwaber and Jeff Sutherland, the co-creators of Scrum, updated the Scrum Guide. The update focuses on the framework, rules, and ceremonies of Scrum, removing specifics about strategies and techniques. An accompanying Scrum Update document provides a statement of refinements that clarifies some of the finer points of the Scrum Framework.
The Scrum Alliance announced plans to strengthen the Certified Scrum Professional (CSP) designation into "a certification program that meets worldwide standards for structure and testing required for accreditation." The CSP designation, goes beyond the CSM as it requires experience applying agile in the workplace. Details for a beta program will be in the next Scrum Alliance Newsletter.