If shorter release cycle could be considered as a success for Agile software development teams, they might be considered as an issue if the other parts of the organization are not ready to handle this. In this article, Colleen Johnson shares an experience where the successes achieved implementing the Kanban method at the team level were leveraged to expand them to the enterprise level.
This is about agile “anti-patterns”: “something that looks like a good idea, but which backfires badly when applied” (Coplien). The presenter has been around Agile development from before it was called Agile. In that time, he has seen teams fall into the trap of many of these anti-patterns, becoming stuck without ever realizing it.
Scrum Days Poland is a two-day conference focused on Scrum and Agile project management approaches. It aims to create an environment where people can meet, build social networks, do business and have fun with a new conference experience. The conference also provides an executive track with talks about leadership, organizational change and managing companies.
Retromat is a free online website that allows to generate random plans for Agile and Scrum retrospectives. Out of a pool of more than 100 activities, it selects one for each of the five phases (stage setting, data gathering, insight generating, decision, conclusion) to create a retrospective plan.
The Agile Coach Camp is a three-day conference about Agile Coaching run by agile coaches for agile coaches based on peer-to-peer learning and exploration in an OpenSpace setting.
If Scrum is the king of the Agile software development frameworks, Kanban can be defined as a distant cousin. We know that there are some connections through this Lean parents, but we don’t always known what it looks like exactly and when to use it. If you want to have a clear and quick (60 pages) understanding of what Kanban is, then this Kanban Workbook is for you.
In the Agile world, software architecture is about making design decisions with just enough anticipation. Too much anticipation leads to overly heavy architectural constructs that may never be used (YAGNI); too little anticipation leads to expensive refactoring and potentially fatal build-up of technical debt. This session presents an approach for Agile architecture roadmapping with just enough anticipation.
Scrum Expert Copyright © 2009-2024 Martinig & Associates