Agile Reality over Rhetoric
In this blog post, Scott Ambler discusses the rhetoric that he has found to be the most misleading for people trying to be effective at adopting agile techniques.
Knowledge
Articles, Blog Posts, Books and Quotes on Agile Project Management
How Product Designer Works in Agile Teams
The product designer (PD) is very a important role in software development. They will provide detail requirements specification and business workflow, UI workflow. In traditional software development process, PD will prepare the detail requirement design document before develop team start to make software design. How does the product designer work in Agile Teams?
Openness Given and Received
It’s important for people to believe that openness given can lead to openness received. This openness must extend to admitting mistakes when necessary. […] When people admit to mistakes, others in a group are more apt to do so as well. It’s always better to know about mistakes earlier than later. Being open about them has the added benefit of giving critics less ammunition.
Large, Multisite and Offshore Agile Projects
“After working for some years in the domains of large, multisite, and offshore development, we have distilled our experience and advice down to the following: Don’t’ do it.” “Scaling Lean & Agile Development – Thinking and Organizational Tools for Large-Scale Scrum”, Craig Larman & Bas Vodde, Addison -Wesley
My Product Owner Will Kick Ass
This blog post is about what a great Product Owner should be like.
What Scrum Can and Cannot Fix
When introducing the concept of Scrum to an organization for the first time, I try to give a reasonably unbiased view of what to expect. I warn the new Product Owner that at first he may feel overwhelmed and struggle to articulate requirements in a clear and actionable fashion. I tell the new ScrumMaster that the innocuous duty assignment “ensure everyone follows the Scrum process” may make her wildly unpopular for a while. I also like to be clear with everyone which problems Scrum can fix and which it cannot.
The Core Protocols, an Experience Report – Part 2
The Core Protocols are our ‘best practices’ for people, teams of people and organizations that want to get great results – all the time. They are ‘Core’ because they are foundational – they can be used by all teams, anywhere, even if you already have organizational patterns and best practices of your own. They are ‘Protocols’ because they name and prescribe ways that people can interact (behavior), predictably, like the ‘protocols’ followed in diplomacy.