Retrospectives are often considered to be a valuable agile technique, but sometimes teams have difficulties doing them: insufficient control of things, thinking that they can’t improve, difficulties defining good actions, or much complaining. Teams may find retrospectives boring, and a waste of their time. How to deal with this, and help teams to discover better ways to do retrospectives?
Collaboration between developers and testers is often considered important in cross functional agile teams to become successful. There is also a benefit of having independence for testers, so that they can report about the quality of the software without fear. How can you balance testers independence with collaboration in agile teams?
Martin Fowler talked about software development in the 21st century, discussing agile essence and how teams adopt agile. He presented at the GOTO Amsterdam 2013 conference how teams can increase their agile fluency, from a first star level up to four stars.
The first day of DevOps Days Amsterdam had its focus split between continuous delivery and promoting a DevOps culture. Talks focused on how to automate the deployment pipeline but also system recovery in case of failure. On the culture side leveraging distinct personality types to successfully introduce changes and the positive impact of strong company culture on hiring were some of the takeaways.
Inspired by the photo “Melly Shum hates her job”, Jurgen Appelo, Maarten Volders and Vasco Duarto initiated Happy Melly with the purpose to help people to become happy workers and live better lives. The Happy Melly business has now taken off to help organizations to survive in changing environments, with happy workers that are motivated to engage and contribute.
Collaboration between business and IT can be a problem in enterprises. People are finding ways to better support the business needs and increase the business value of IT, using business IT fusion, DevOps or sociocracy.
Collaboration between agile team members, like developers and testers, helps to make teams successful. What can scrum masters do to help testers and developers to work together in agile teams, and improve collaboration?
Impediments are used to discuss issues take actions when a team becomes blocked. Impediments are handled in different ways, a look at how some scrum masters do it.
Retrospectives help teams to learn and improve their way of working. Several agile coaches have scaled retrospectives to cover larger projects or programs with multiple teams. Let’s explore how they did it.
Organizations that implement self-organized agile teams need managers who empowerer the teams by using servant leadership, and who coach and mentor them to learn and continuously improve themselves.
The Appsecute platform aims to improve collaboration and increase productivity through consolidating information associated to an applications lifecycle. The software as a service platform accepts messages directly from people and from integrated technology platforms, then it aggregates those events online for viewing by everyone within an organization.
Having stable teams can be beneficial for agile software development. Several views on establishing and nurturing stable teams, and dealing with team dysfunctions.
Swarming is a technique that helps agile teams to deliver working software fast and frequently. What is swarming, what are the benefits of swarming, and when and how to apply it?
To become more flexible, durable and increase organizational effectiveness, retrospectives can be used in adopting agile. Some experiences stories and examples of how teams use retrospectives as a sustainable and adaptable solution for agile adoption, to implement continuous improvement with them.
In an agile adoption, there is need to develop and sustain an agile culture. What can the Human Resources department or managers do to support the agile in their company, and lower the chance on employees concerns about their roles, assessments of their performance, and on their work environment?