Here are all 248 of my posts:
Expand All
- March 2016 (2)
- February 2016 (1)
- January 2016 (4)
- December 2015 (5)
- 29: Albert Einstein would have liked Retrospectives (0)
- 21: Focus – “If you chase two rabbits, you will not catch either one” (0)
- 14: Shaping a team – Get good people and put them in the right role (0)
- 07: Unfortunately Corporations Equate Weight of Paper with Safety (2)
- 01: User Stories are Experiments (0)
- November 2015 (4)
- October 2015 (3)
- September 2015 (5)
- August 2015 (4)
- July 2015 (4)
- June 2015 (5)
- 29: Continuous Delivery by Default; Timeboxes by Exception (0)
- 22: Programmes can use more than one method: Kanban, Scrum, XP, BDD, etc (2)
- 15: Product Owner – leader, facilitator or unnecessary overhead? (0)
- 08: Test driven architecture – use your tests to inform architecture (0)
- 01: 35 person-years worth of prototype is a fantastic spec (2)
- May 2015 (4)
- April 2015 (4)
- March 2015 (5)
- 30: 4Ls Retro Format – Liked, Learned, Lacked, and Longed for (0)
- 23: I hate part time assignments to projects; they challenge WIP limits (0)
- 16: I always work with a “Product Owner”; never a “Scrum Product Owner” (0)
- 09: Don’t use the Formal User Story Format for Minor Modifications (0)
- 02: ERIC Grid – Blue Ocean Strategy for Departmental Transformation (0)
- February 2015 (4)
- January 2015 (4)
- December 2014 (5)
- November 2014 (4)
- October 2014 (4)
- September 2014 (4)
- August 2014 (4)
- July 2014 (4)
- June 2014 (5)
- 30: My four days of silence surrounded by developers (3)
- 23: Product at the end of its life cycle? Try the Scream Test (0)
- 16: PMs Need a Technical Ally When Introducing Automated Testing (0)
- 09: Nine Things to do When Nobody on Your New Team Knows Lean-Agile (0)
- 02: Four Reasons to Book Regular One-to-One Meetings (0)
- May 2014 (4)
- April 2014 (4)
- March 2014 (5)
- 31: Plug for Henrik Kniberg’s Agile Product Ownership in a nutshell (1)
- 24: Agile has Lists but isn’t Lists (0)
- 17: Improve Customer Collaboration with Ubiquitous language (0)
- 10: What to do when a developer produces too many bugs (0)
- 03: Lean-Agile is micromanagement but not in an excessive way (0)
- February 2014 (4)
- January 2014 (4)
- December 2013 (5)
- 30: Are you dead? A comfortable Agile Project Manager isn’t doing their job (0)
- 23: Bucking Bronco: Software Projects that Kick (0)
- 16: Declarative vs Imperative Gherkin Scenarios for Cucumber (2)
- 09: Developers don’t have time for code reviews and unit tests (1)
- 02: Fluid Planning and Execution Creates Agility (0)
- November 2013 (4)
- 25: Whose responsibility is testing anyway? (0)
- 14: Cake Driven Development (0)
- 11: No space to co-locate team – think again (2)
- 04: Avoid the Refactoring Branch of Doom (0)
- October 2013 (4)
- September 2013 (5)
- August 2013 (4)
- July 2013 (5)
- 29: Kanban in Video, Post and Book (3)
- 22: Research on Pair Programming by Professionals (14)
- 15: Six Reasons to Adopt Specification by Example (0)
- 08: 90% Complete not = Done (0)
- 01: Daily Plan: Stand up to Plan the Day (0)
- June 2013 (4)
- May 2013 (4)
- April 2013 (5)
- March 2013 (4)
- February 2013 (4)
- January 2013 (5)
- 28: Agile MSP Programmes with Rigid Projects. Ouch! (0)
- 23: Speaking at the BBC Cardiff Kanban Meet Up (2)
- 21: Benefits Map: Impact Mapping for Programme Managers (4)
- 14: Three Strategies when the Product Owner is Disengaged (0)
- 07: MSP Agility Scorecard: How MSP Shapes up against the Agile Manifesto (0)
- December 2012 (5)
- November 2012 (4)
- October 2012 (5)
- September 2012 (4)
- August 2012 (4)
- 22: Opportunity Assessment – 10 Questions to Evaluate Proposed Features and Projects (0)
- 15: Software Craftsmanship should be Professionalism and a Dedication to Improvement (0)
- 08: Three Options When the Boss Changes Priorities Mid-Sprint (0)
- 01: Rugby is a Better Analogy for Agile Delivery than the Scrum (11)
- July 2012 (6)
- 30: Use a WIP Limit During a Sprint to Avoid the Cataract of Stealth (0)
- 23: A Lean-Agile Perspective at the Project Research Institute (part 2) (0)
- 22: Programme Management: Build capability, Roll it out, and Deliver Business Benefit (0)
- 15: Is Software Craftsmanship a Type of Martial Arts? (0)
- 08: Nine Common Strategies for Managing a Growing Defect Backlog (3)
- 01: Reporting Success Stories Alongside Formal Benefits (0)
- June 2012 (4)
- 29: Normal Service Resumed (0)
- 15: Software Craftsmanship is an Apprentice’s Journey to Guild Master (1)
- 08: What do I do When … ? (3)
- 01: Can Cucumber save Raja? (0)
- May 2012 (2)
- April 2012 (2)
- March 2012 (2)
- 15: Software Craftsmanship is not writing crap (0)
- 01: Agile Infrastructure (4)
- February 2012 (2)
- January 2012 (2)
- December 2011 (2)
- November 2011 (2)
- October 2011 (2)
- September 2011 (2)
- 15: Foot in the Door Technique (0)
- 01: Declaration of Interdependence (0)
- August 2011 (2)
- July 2011 (1)
- March 2011 (2)
- 15: Change is Good for Agile Projects (0)
- 15: Programme versus Project Risks (2)
- December 2010 (1)
- 02: Build it in a Week (0)
- October 2010 (1)
- 21: Glossary definition for “Agile” (0)
- September 2010 (2)
- 12: Using a Product Led Matrix in Lean-Agile (0)
- 11: Minimum Releasable Feature (4)
- August 2010 (2)
- May 2010 (1)
- June 2008 (10)
- 24: Agile Quality Management (1)
- 19: Agile Project Estimating (8)
- 17: Agile Project Execution (0)
- 16: Agile Project Monitoring and Control (2)
- 08: Agile Roles and Responsibilities (3)
- 06: Agile Change Management (0)
- 06: Agile Project Closure (0)
- 06: Agile Post-project (0)
- 03: Agile Project Planning (2)
- 03: Agile Pre-project (1)
- May 2008 (8)
- 31: Agile Project Scope (1)
- 30: Agile Project Management (0)
- 29: Agile Gotchas (0)
- 29: Agile Project Initiation (9)
- 29: Agile Lifecycle / Agile Heartbeat (0)
- 28: Evidence for Agile (0)
- 28: Agile Terminology Comparison (0)
- 28: Agile Risk Management (4)
- November 2007 (1)
- September 2005 (1)
- March 2005 (1)
- December 2004 (1)
- April 2002 (1)
- 19: An Agile Comparison (1)
- March 2002 (1)
- 05: Controlled Scope Management (1)