Ron Jeffries is well known. He’s so well known that he doesn’t even have to tell you who he is. You should just know. A quick trip to his Twitter page tells you that. #ronjeffries #pwnd
Regardless, we always perk up whenever we read something he has to say. Usually it’s pretty interesting stuff. His latest blog entry tells us that we do not need technical user stories. Period.
Why is that?
Let’s break it down for the rest of us peons, shall we?
“One of the pillars of Scrum is for the Product Owner (PO) to prioritize work for the team, so that the best possible product can be delivered within the desired time and budget. Clearly, the PO is (should be) capable of pinpointing the most value. Therefore, it isn’t too smart for a development team to focus on anything other than what the PO wants.”
Since technical user stories have the promise of providing faster velocity in the future, and are different from the PO’s user stories, you end up having a priority and time dilemma: PO user stories VS. Technical user stories.
Ron Jeffries 3 Reasons to NOT Have Technical User Stories
As developers, we are, at the end of the day, the critical path between completion and non-completion of a project. I mean, let’s face it. If we didn’t do our jobs, all the project managers out there would be out of a job! (I kid, I kid!)
Russ Sherk, a developer at Klocwork, tells us about the 5 biggest ways to waste time as a developer and what to do. Not only does Russ give us the ways to fix the issue, we’d like to add on a couple of pointers on how Agile can help with time-wasting for developers too.
I absolutely love this service. Why? Because I had this idea last year and dang near built it myself! I’m always interested in going to the coolest tech conferences and any local Agile events that I can get to. But there isn’t a really good site out there that provides all of that information.