Archives

Enabling Specifications

I recommend using the ‘Enabling Specification’ practice. This is NOT part of the bare framework of Scrum. But it is a frequently recommended practice. Typically recommended. This is: Just-enough, just-in-time documentation. Meaning that the implementers in the Scrum Team have enough information to build the user story correctly the first time. Or at least they […]

Read More »

The Team is primary

There has been a lot of discussion in the community lately about scaling.  With specific discussion of the SAFe and LeSS frameworks. I don’t have a strong opinion on many of the issues. I do think each scaling situation is different.  I do think the music (the values and principles inside the players) is at […]

Read More »

Sample Impediments (RDU)

Just did a course in Raleigh-Durham.  Here are some impediments the group identified…. Lack of people Turnover in staff Unclear scope Requirements changing too much Cutting corners Lack of communication with customer Bureaucracy – pessimistic stakeholders Poor morale Manage by fear Budget (insufficient) Lack of visibility Lack of management skill Dependencies (other projects) Traceability (lack […]

Read More »

Managing self-organizing teams

How do we suggest that managers …well… manage self-organizing teams? By self-organizing, I also mean self-managing.  Let’s assume that not all ‘self-organizing teams’ will self-organize or self-manage effectively. So, a few suggestions. 1. Get rid of almost all the old stuff. I really want you to think about getting rid of it all.  I cannot […]

Read More »

Why I prefer ScrumBan to Kanban

I have spoken about why I like Lean and why I like ScrumBan, a combination of Scrum and Kanban. Some people prefer ‘Kanban’, as it is being called in the software development community.  Sometimes: Kanban Method. To be honest, I think I know what Kanban is in Lean Manufacturing. But I am unsure what ‘Kanban’ […]

Read More »

Story Points rather than hours

Jeff Sutherland has a great post about this, here.  A must read.    

Read More »

3 Methods to increase Business Value

Yesterday I enjoyed talking to Southern Fried Agile, the local one-day agile conference in Charlotte.  My topic was: Three Steps Toward Greater Business Value. I was pleased to see many participants wanted to discuss this subject. So much so, that the organizers decided to run the session twice. I am happy this is considered an […]

Read More »

Choosing a Scrum course/trainer

This is a question I get from time to time: How should I choose between one course/trainer and another? This is an important question and deserves some thought.  It does not deserve, in my opinion, a simple answer, as one might get from Zagat’s about a restaurant. The choice is different than choosing yet another […]

Read More »

The Team and the Implementer Role

There has been, in several places, some good discussion about the roles in Scrum.  And often the discussion turns (explicitly or implicitly) to ‘what is the Team and what does it mean?’ The Team The full team is what is most important.  Product Owner (PO), ScrumMaster (SM), and Implementers.  Together.  About 7 in total. Ideally […]

Read More »

The PO – The Team – The Daily Scrum

I have some different views on this topic, and wanted to share them. Your comments are of course welcome. I am NOT asking what is or should be in the Scrum Guide. Or whichever ‘scrum bible’ you use. (In general, I prefer the Scrum Guide.) I am sharing my thoughts and experiences, together, taught me.  […]

Read More »