The introduction and integration of agile approaches to an organization should be regarded and treated as an agile project itself says Andreas Schliep. An interview with Andreas about pitfalls when trying to scale agile, on ScALeD and how it compares to Agility Path, LeSS, SAFe and DaD, and on continuous improvement and scaling retrospectives.
Teams consist of individuals working together. Individuals have their own specific beliefs and perceptions. If you know where a person’s perceptions are coming from, you can better understand why they see things different than you do and behave in a certain way. Being able to understand people helps to find better ways to collaborate and communicate in teams.
Metrics are engrained in kanban. They play a role in several kanban practices like visualizing and managing flow, and support the agenda’s for sustainability, service orientation and survivability. At the Lean Kanban Central Europe 2014 Conference Wolfgang Wiedenroth talked about the power of metrics. In his presentation he provided may examples of using metrics with kanban.
Teams can become so focused that they forget the world around them and risk losing contact with stakeholders. This makes it difficult for them to know what their customers need and how end users will use their products. At the ASAS2014 conference Daisy Rasing-de Joode will show how successful agile teams create synergy by being interdependent and highly collaborative with their environment.
Continuous learning supports agile adoption in enterprises. A culture change can be needed to enable and support continuous learning. There are several things that managers and agile coaches can do to establish and nurture a continuous learning culture.
Developing and delivering products which customers don’t want and for which there is no market can be costly. Agile can help you to efficiently develop products, but you need to know what to build. How can you find out which products your customers need?
Roman Pichler shared his views on product owner’s participation in sprint retrospective to increase collaboration with development team.
Software delivery in a modern company requires autonomy to make releasing software easy. Niek Bartholomeus gave the presentation orchestration in meatspace at the DevOps Summit in Amsterdam where he discussed how can we change enterprises from orchestration to a more autonomous approach, in order to speed up the feedback cycle from idea to production.
A report on how happiness index could be scaled out from team level to organization level. Frank Schlesinger, Corinna Baldauf and Stowe Boyd shared their experiences of scaling the happiness index and tools for implementation.
The build-measure-learn feedback loop in lean startup aims to help entrepreneurs to learn about the needs of their customers. Agile retrospectives are a way to reflect and learn and to agree on changes that are needed. Some examples describing how lean startup can be supported with agile retrospectives to learn and take actions.
Everything Sysadmin proposes five milestones, each with a set of detailed checklists, to help an organization adopt a DevOps culture. The site places these milestones within the context of The Three Ways, a set of principles popularized by “The Phoenix Project”.
Agile retrospectives are used by teams to improve their performance, by reflecting on the way of working and defining improvement actions. But retrospectives can also be used for personal improvement, additional to or as a replacement of performance appraisals. Such retrospectives can be done as a one-on-one by a manager and an employee, individually by an employee, or in a team.
Jake Benilov will give a talk on September 27 at Agile Tour Brussels about feedback techniques used for making gov.uk. InfoQ did an interview with Jake about using the feedback techniques and how the team applies lean startup with minimum viable products to do user research.
When enterprises implement agile ways of working, questions can arise if changes are needed in the way performance appraisals are being done? Several authors have suggestions on how you can use feedback next or as a replacement for existing appraisal processes, to improve the performance of individuals and teams.
There are different types of pivots possible in lean startup, which help you to decide whether to persevere or pivot during product development. They each with their own purpose and ways to use them. Let’s explore some of them to see when and how you can pivot? Or maybe have to decide that it’s better to quit?