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.
What are the advantages and disadvantages of having the same person fill both the Product Owner and the ScrumMaster role on the same Scrum project? Is this really a workable option?
How do you work with difficult and uncooperative people? People who are combative or unprofessional? People who seem actively opposed to the agenda?
Does a ScrumMaster need a technical background? Do they need to be able to read code and coach developers on their day to day work?
Scrum and agile certification is now very much in focus. The 'certification story' is unfolding to become a major subject of debate in 2010. The story has several facets, with action from the Scrum Alliance, Scrum.org and the community-at-large, including notable bloggers and the Agile Skills Project. At issue is the basic value of certification.
Scrum Certification is one debate that refuses to die down. First, it was about the hollow nature of certification for which there was a comment “Pay the tuition, sit through a couple days of class, and you're in”. Subsequently a new format was devised, which too failed to enthuse the Agilists who were against this certification philosophy. Is there another makeover on the anvil?
A ScrumMaster as the name suggests is the guardian of the scrum process. He is a change agent supporting his team and socializing Scrum throughout the organization. He ensures smooth functioning of the team by eradicating impediments and keeping the team shielded from distractions. However, in certain scenarios, Agile teams feel that the Scrum Master is the biggest impediment.