Subscribe
Search
Follow me on Twitter
- RT @f4p_dja: With every new book the expectation bar is raised. It's scary to send something to production. We'll edit for 10 more days @az… 56 minutes ago
- Menzies aviation motto: excellence from touchdown to takeoff (note, not from takeoff to touchdown). #f4p 10 hours ago
- @ofinker Indeed! @f4p_dja 1 day ago
- @f4p_dja yes, the company used a common vanity metric as a KPI, resulting in poor service 1 day ago
- Mention a company as an example when writing a book. The company goes bankrupt before the book is finished. #f4p 1 day ago
-
Recent Posts
- Happy 50th Birthday, David J Anderson!
- Fitness for Purpose Diary, Part 3: Replace Scale with Taxonomy
- Fitness-for-Purpose Diary, Part 2: Segmentation
- Fitness-for-Purpose Diary, Part 1: Starting With (and moving away from) NPS
- Knowledge Discovery Process Revisited
- Kanban Is Not a Card, It’s a Space
- Forecasting Cards
- Kanban Guide Is Here – How Not To Read It
- Carlos Goes Agile
Archives
- April 2017
- January 2017
- September 2016
- February 2016
- January 2016
- May 2015
- April 2015
- September 2014
- August 2014
- April 2014
- March 2014
- January 2014
- September 2013
- August 2013
- July 2013
- June 2013
- May 2013
- April 2013
- March 2013
- February 2013
- October 2012
- September 2012
- July 2012
- May 2012
- January 2012
- November 2011
- October 2011
- July 2011
- June 2011
- May 2011
- April 2011
Categories
- Agile (1)
- big picture (1)
- blog (1)
- Blogging (1)
- books (3)
- coaching (4)
- conferences (15)
- Consulting (2)
- decision making (2)
- Enterprise Services Planning (3)
- facilitation (3)
- hands-on (22)
- Improvement (1)
- Kanban (30)
- leadership (1)
- Learning (1)
- life (7)
- tips (1)
- training (6)
- Uncategorized (4)
- user groups (1)
Monthly Archives: May 2011
When Defensive Programming Doesn’t Work
When you’re writing software that interacts with another system, do you really know how that system behaves when it encounters errors? Do you really know what happens when you call IFooRepository.GetFoo(), which is supposed to return an object of class … Continue reading
Posted in hands-on
Leave a comment
When Writing a User Story, Write It on a Card
This is a quick follow-up to the earlier post, When Writing a User Story, Always Start with the User Persona. The post was about a pseudo-user story (“as an application, I want to invoke an API to get grades from … Continue reading
Posted in hands-on
Leave a comment
When Writing a User Story, Always Start with the User Persona
I’ve recently come across a “user story” in an electronic project-management tool: “As an application, I want to invoke an API to get grades from a course.” An experienced agilist will notice right away that this “story” lacks a user … Continue reading
Posted in hands-on
Leave a comment
