Scrum is a simple and lightweight methodology therefore, scrum alone is not enough.
Agile is not meant only for software development. People implement Agile practices in their personal lives too. This post talks about implementation of Agile at home.
InfoQ did an interview with Gil Zilberfeld about better ways to do product planning and tracking, his thoughts about #noestimates, including value in product planning discussions, and how to improve decision making in product development.
Tomas Rybing, Director, Project Management at Aptilo Networks, proposed a prioritization technique called ‘Priority Pyramid’, in agile environment.
InfoQ did an interview with Gil Zilberfeld about managing the expectations that organizations have of agile and how to prevent misconceptions, valuable ideas and practices from agile and what the future will bring for agile.
The gap in agile adoption between Eastern Europe and the US and Western Europe is becoming smaller. Scrum is the most widespread framework, Kanban adoption is growing and SAFe, LeSS, DAD are trending. The way that companies are transitioning to agile is significantly different in Eastern Europe.
There are some alternative ways of identifying different classes of service in kanban. This post talks about these methods.
Yuval Yeret is a senior enterprise Agile Coach at AgileSparks. At the upcoming Agile India conference he is talking on good and bad ways to kickstart agile the Kanban way. He spoke to InfoQ about the synergies between Kanban and DevOps.
“An agile enterprise is able to anticipate and respond swiftly to changes in the marketplace” says Scott Ambler. InfQ interviewed Scott about the reasons why agile projects are failing, how to increase budgets for building new systems, disciplined DevOps, harmonizing agile and lean, and on coaching for enterprise agility.
Recently we polled a small group of InfoQ editors, consultants and trainers asking them for their thoughts on the state of Agile adoption and what ideas, practices or techniques are emerging or being recognised as useful at the end of 2014. This is not a scientific study, rather an informal collection of opinions.
Kanban talks about limiting work in progress (WIP) as a way to manage workflow. “Limiting WIP is hard enough, but selling it can be nearly impossible” said Jim Benson. At the Lean Kanban Central Europe 2014 Conference he talked about how to convince others to limit WIP.
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.
Kanban is often used to manage work, but the concepts of kanban can also be used to guide a journey of change in an organization. This is a case study of an insurance company that used kanban to get change done to improve visibility and predictability and engaging their people.
When organization use kanban mainly for visualization of the work they may be missing out on benefits, says Matthew Philip. Introducing a flow manager role can help teams to reflect and find solutions to the problems that they are facing, thus catalyzing change in the organization.
Blockades in work, like insufficient information, unclear requirements or having to wait for tools or systems to become available can have a systematic cause. It could be the case that similar problems that block the team keep happening until the underlying causes are addressed. You can use your blockades as treasures of improvement to sustainably improve the way work is done.