Microsoft has announced Teams, a group collaboration workspace based on chats and integrated with Office 365. Developers have the opportunity to extend Teams with Tabs, Bots and Connectors.
Esther Derby identifies six rules to use when change needs to happen, so that the people involved are honored, and the complexity of the change is acknowledged. Creating an environment based on empathy, knowledge of the past, and a willingness to experiment, makes change less stressful.
People are hardwired to instantly decide who we trust, but also to work collaboratively in small groups. Cognitive biases can get in the way of collaboration, but when you understand how these biases work and what agile practices can do to help, you are more likely to build better interpersonal relationships and create successful products.
In a presentation for OnAgile 2016, Johanna Rothman states that thinking small, and building upon the informal communication networks already at play in an organization, can help scale practices to manage large programs. Rothman provides advice on planning, architectural design, and measuring progress.
Once a startup becomes successful it needs to scale its teams and technology to grow. Scaling has to be done in way that the startup remains effective, and thus capable of quickly delivering products to satisfy the needs of the fast growing user base. Some of the challenges faced are hiring people and onboarding them, along with technology decisions that allow you to grow and get the right people.
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.