InfoQ Homepage Continuous Improvement Content on InfoQ
-
Should Teams Decouple Cadences?
Recently a Twitter discussion took place about allowing teams to have multiple cadences, for instance by using a different rhythm for planning the work and for learning and improving. Decoupling cadences gives teams room to explore and learn what works best for them; it can lead to more adaptability and autonomy and better outcomes.
-
Post-Mortems Trends and Behaviors
Eric Siegler presented his findings at Velocity from analyzing data from 1000 post-mortems ran by 125 different organizations over a six month period. Main trends include the prevalence of blameless post-mortems; the fact that only 1 in 100 post-mortems refer to "human error"; and that analyzing the lifecycle of incidents can provide useful insights on weaknesses in the incident response process.
-
XebiaLabs Announce DevOps Intelligence Engine
XebiaLabs, the developers of Continuous Delivery and DevOps tooling XL Release and XL Deploy, has announced availability of the first release of XL Impact, a goal-based, data-driven recommendation and decision making tool for DevOps organisations. XebiaLabs claims this is the first tool of its kind and the capability is essential for organisations to prove DevOps performance improvements.
-
Q&A with Ken Schwaber and Jeff Sutherland about Scrum Guide Updates
The Scrum guide has been updated to better reflect what Scrum is and clear up misconceptions. Scrum can be used for building software products, and it can be applied to many other areas outside of software as well. Scrum is a framework based on empiricism for continuous improvement. Having a potentially shippable product increment at least every sprint or more often is a key element of Scrum.
-
Q&A with Aurynn Shaw on Sharing Her Personal DevOps Journey at DevOpsDays NZ
Raf Gemmail speaks with Aurynn Shaw about her upcoming DevOpsDays NZ talk and the humanist side of DevOps.
-
Q&A with Alison Polton-Simon on Her 'Metrics That Matter’ Talk for DevOpsDays NZ
Raf Gemmail talks with ThoughtWorks’ Alison Polton-Simon about her DevOpsDaysNZ talk on metrics which teams should be measuring.
-
Perfect Software, Measuring Continuous Delivery, and Exploring the Future: Agile on the Beach 2017
At Agile on the Beach 2017, the key takeaways from the final afternoon of the conference included: delivery teams can add value more rapidly by embracing lean, iterative and continuous deployment methodologies; and although highly beneficial, implementing continuous delivery is hard due to the need for principles to be applied in your context.
-
First Annual Retrospective Report Published
The First Annual Retrospective Report provides a deeper understanding of how retrospectives are used in the real world. The results indicate that retrospectives lead to improved team communication and productivity and help to create an environment of trust. Major challenges are that topics discussed cannot be solved by the team and people do not feel comfortable speaking up.
-
How the Financial Industry Is Doing DevOps
The second DevOps Enterprise Summit (DOES) Europe, once again held in London, brought together the DevOps enterprise community. The financial industry was well represented, giving the attendees a unique perspective on the challenges facing this heavily regulated industry and how DevOps is helping to address them.
-
Fearless Feedback for Software Teams
Feedback builds trust, increases team cohesion, and helps individuals to improve their skills and grow in their craft. An effective feedback cycle is the best possible tool for improving team performance. With feedback, issues are addressed before they become toxic and mistakes can be course-corrected early on.
-
Atlassian Opens up Team Health Monitors and Team Playbook Blueprints
After introducing a tool-agnostic version of its Team Health Monitors at Summit 2016, Atlassian now also bundles Team Playbook blueprints with the recently released Confluence Server 6.1. A Health Monitor workshop is a team self-assessment aiming to identify pain points and formulate a plan to address weak spots by running low-ceremony "plays" that "can help improve a team's overall health".
-
Applying Hoshin Kanri at Toyota
Toyota uses Hoshin Kanri to give direction on where they want to improve using Lean IT. Employees at various levels can exchange ideas about Hoshin items, and potentially get them approved by higher management. This approach makes results stronger and increases buy- in from the employees who contribute upfront.
-
Lean and Agile Culture at the Finnish Broadcasting Company Yle
Scaling lean and agile is not a question of frameworks, it's about values, principles and mindset. At Yle the company management has been involved in the agile transformation by carrying out experiments, learning and doing; not by implementing frameworks. Magic happens when you work together with people in teams on all levels.
-
Driving Improvements with Lean Pilots
Lean, agile and Lean Startup can strengthen each other for driving improvement. Lean Pilots, a data-driven improvement framework for removing major cross-functional organizational impediments, has been used to drive internal continuous improvement.
-
Organizing Improvements with Lean Leadership at ING Bank
It’s the manager’s job to organize improvements and to make sure that real learnings take place. For real learnings you must accept the unknown and move outside of your knowledge boundary. Agile, lean and continuous delivery help to boost your learning capabilities.