This article (first published on infoQ) explores why estimating is useful, why we use story points (and what they are), and the latest discussions around #NoEstimates.
Announcing the launch of Sophorum, a business agility service for business analysis, coaching, team leading, new product development, business design, education, etc.
Fed up with the recent negativity around agile methodologies? Between Enterprise Scrum and Scaled Agile Framework? This is my take.
At last it has a name. Gartner’s pace-layered application strategy framework provides a model that allows waterfall and agile practices to live side-by-side.
This talk, which followed my article ‘Bringing sexy back to governance‘, was presented at the 2012 BA Development Day conference, and covers what we mean by governance, what the fifty shades are, and what we can all do about it – in short, this is a call to action for lean governance.
Ever wondered why big organisations seem so risk-averse and rely so much on heavy-handed governance to protect themselves from spending shareholder money unwisely? Did you also ask yourself why this approach simply introduces a different type of risk, and is there a better way? If so, read on …
Sometimes adopting agile practices can be a precarious activity, a balancing act, and without the right training or support, like walking blindfolded across a tightrope.
No matter how attractive it seems to just dive in and get started, it still makes sense sometimes to pause first and make sure it is the right thing to do.
As I have worked on the ‘Agile Extension to the Business Analysis Body of Knowledge‘ over the last year, I have repeatedly come across the assertion–by many agile practitioners–that we no longer need gate meetings on projects. From my experience in leading project governance this confused and concerned me, so I have looked into this and believe I have discovered why[…]
At the Agile2010 conference in Orlando the International Institute for Business Analysis (IIBA) released a draft of the Agile Extension to the Business Analysis Body of Knowledge (BABOK) — introducing how business analysis on agile projects changes from traditional/waterfall approaches.