Experienced Scrum Masters explain how they define and measure their own personal success as Scrum Masters, and share their lessons learned about how to achieve success. From dealing with stakeholders, to how to improve coaching skills and how to help the team achieve a sustainable pace, the lessons come from many years of experience and will help you improve your performance as a Scrum Master.
The book Improving Software Development Productivity contains practices, models and case studies to quantitatively support adoption of agile software development. An interview with Randall Jensen about measuring and improving productivity, contribution of agile to productivity, benefits from pair programming and teams, knowledge retention in maintenance and commandments for communication.
This article will explain a different approach to traditional Multi User Performance testing; using the same tools but combine them with modern data visualisation techniques to gain early insight into location specific performance and application areas that may have "sleeping" performance issues.
Rally Software and Carnegie Mellon's Software Engineering Institute (SEI) are researching the impact of agile software development practices. An interview wit Larry Maccherone and Jim McCurley. 1
An interview about applying strength-based techniques like appreciative inquiry, solution focused, positive deviance and 5-why's with Lean Six Sigma, and measuring performance in organizations.
The book "The Agile Culture" describes how you can develop a culture of energy and innovation, and provides tools to build trust, take ownership and deal with walls and resistance in organizations. 3
Lean has proved to be instrumental in moving beyond Agile with a practice of continuous improvement distincting between bugs and problems that directly effects on team performance and engagement. 2
This second article in the “3 years of Kanban at Sandvik IT” series focuses on the lessons that the System Development Office learned when sustaining the Kanban method during this 4 years journey. 1
The story of an internally driven and remarkably smooth Kanban implementation approach which quickly rewarded Siemens with real and sustainable improvements in predictability, efficiency and quality. 15
InfoQ interviewed Capers Jones about advancements and events in software engineering and the effects that they have had on our society.
Some 80% of all improvement and change programmes fail. Intelligent Evolution ensures long-term business success rather than short-term satisfaction of a standard or theory.
Feedback is not the same as prediction. Data does not tell us what to do – it simply indicates a problem. Feedback underpins much of the Agile Manifesto. Feedback guides how we deliver iteratively. 1