Visualize everything, pair up, open Friday, and no training budget; these are some of the "work hacks" that have improved work life at Sipgate, a telephone provider using Scrum.
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".
Safe-to-fail experiments can be used in complex environments to probe, sense, and respond. You have to know what success and failure look like and need to be able to dampen or amplify the effect of probing to handle potential failures. Safe-to-fail experiments can help you to deal with risks and uncertainty, learn, and keep your options open.
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.
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.
The agile paradigm adapts processes to human nature, in contrast to the classical management approach which obliges team members to adjust to a particular development process. Bateson's learning model can help us to go from doing agile - following an agile method - to being agile - having your own agile identity and vision.
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.
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.
Distributed development depends on effective communication: you need to look for ways to have robust and diverse communication, build empathy towards each other to encourage feedback, and keep an eye on motivation. Team members are more engaged and creative when there’s shared ownership and responsibility for complete delivery from idea to production in distributed teams.
People can feel limited when challenged, which slows them down or keeps them from trying. It can be a real problem, but their fear might actually be in their imagination. Sometimes the only thing that's holding you back is yourself. Survival rules can hinder us- sometimes you have to break them.
Feedback can be used to build trust in teams and help individuals improve their skills and grow in their craft. Emily Page and Doug Talbot shared their experiences from experimenting with peer feedback at Ocado Technology at Spark the Change London 2016. An interview with Emily Page, Organizational Catalyst at Ocado Technology.
More and more now value is created through connected organizations and individuals using seamless collaboration across boundaries. At the same time however, many companies are still influenced by management practices invented in 19th century. A paradigm shift is needed to successfully manage in the networked society.
Giving teams autonomy to spend 10% of their time for learning reduces delivery time, increases quality, and increases motivation. The 10% rule gives teams full autonomy to work on things they consider important. It results in freeing up people's creativity and letting teams grow their potential.
The Spotify model can help you to understand how things are done at Spotify, but you shouldn’t copy it in your own organization. It changes all the time as people at Spotify learn and discover new things. There is no one way in which software is developed at Spotify.
If you want continuous improvement you can start with retrospectives, but you must go far beyond that with change management, culture change, and innovation. The most important thing in order to make change happen in organizations is creating new habits and changing your culture.