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.
Lack of autonomy at work is directly related to reduced levels of motivation and engagement, and increased levels of stress and poor health. What can leaders do to improve the sense of autonomy in individuals, thereby increasing levels of motivation and job satisfaction?
To drive operational maturity you need a microservices architecture, continuous delivery process, DevOps culture and platform automation. Together these four help you to transform your whole organization for achieving cloud-native operability to continuously deliver additional value to your customers.
Google researchers studied teams and what traits help with their efficiency. Named Project Aristotle, the study provides insight into what helps teams succeed, such as psychological safety, structure, and a sense of purpose.
At the Agile on the Beach 2016 conference, Elizabeth Pope presented “10% Time: The Pros and Cons”, and discussed her experience of devoting a percentage of work time to R&D and learning, which was popularised by Google with their ‘20% time’. Key learnings included strive to reduce barriers to entry, support non-development teams, and encourage collaboration across the organisation.
Continuous delivery should be treated as an agile project as it is about automating your deployment. You have to speed up in small steps and gain trust by doing small deliveries and solve problems fast. The story about how Klaverblad insurance has implemented Agile, DevOps, continuous delivery, and microservices.
At their massive Dreamforce conference, cloud leader Salesforce.com unveiled Salesforce DX: a new model for building and deploying applications to their platform. InfoQ spoke to VP of Product for Salesforce DX, Wade Wegner, for all the details.
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.
At the Agile on the Beach 2016 conference, held in Cornwall, UK, Rebecca Parsons argued that the requirements for improved time-to-market and increased business agility can be achieved by architecting software for real evolvability, keeping systems poised for change, lowering the cost (and risk) of experimentation, maximising visibility and feedback, and aligning the organisation.
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.
Bias, priming, and salience are the main psychological factors that influence our ability to estimate. Knowing what happens psychologically when we estimate, and using techniques from psychology, helps us to deal with those factors so that we can improve our estimations argued Joseph Pelrine, social complexity scientist and PhD researcher in psychology.
Docker in Action, written by Jeff Nickoloff, provides a comprehensive introduction to Docker and how to integrate it into a development workflow. This book is intended for developers and operations engineers who wish to adopt Docker for application development and integrate it into their software delivery process.
Eduardo Salas is recognized by the APA for his 30 years of research on team work. His implementation of team training includes defining team structure, identifying specific communication needs, clarifying roles and leadership skills, and practicing with scenarios. This technique has been used across many fields of work, and is part of the program as NASA prepares to send a team to Mars.
The Agile Alliance hosted a one-day Executive Forum in San Jose, CA on September 19. The event attracted participants from around the world and a range of senior speakers from large organisations, and focused on how adopting agile development impacts companies and what executives need to do to help ensure successful cultural transformation, which is what agile adoption at scale is about.
When developing a high speed printer based on a new print technology things change often; you need an effective and flexible solution for managing a large project with many different disciplines. Océ Printing Systems decided to customize Scrum and scale it to enable collaboration and make progress transparent.