Derek Davidson PST PSM II CSP

less info
575 reputation
15
bio website webgate.ltd.uk
location Plymouth, United Kingdom
age 54
visits member for 1 year, 7 months
seen Aug 18 at 13:20

I'm a Scrum Trainer, agile coach & consultant. I teach people about Scrum and help businesses implement Scrum.


Aug
8
comment Managing 'done' but not releasable code in TFS
Breaking user stories down in to vertical slices of functionality that are independent and have value is certainly hard. There are many resources from agile authors on how to deal with this. Here's a simple blog article from Rachel Davies, for example: agilecoach.typepad.com/agile-coaching/2010/09/… There are many others, too. Story slicing is a great skill to have in your agile toolbox.
Aug
7
answered Managing 'done' but not releasable code in TFS
Jul
6
answered why the terms used in Scrum are so strange?
Jun
27
answered Coding and testing in the same sprint
Jun
11
answered Reporting defects in Agile
Jun
11
comment Reporting defects in Agile
@JensG Sure, defects occur after work is 'done'. But they usually surface after the sprint in which the work is done. This is simply because work that is done, by definition, has no known defects.
Jun
11
comment Reporting defects in Agile
I'm a little confused as to why you're reporting defects within a sprint. My understanding is that work is 'done' or 'not done' within a sprint. Being 'done' would imply no defects. Not being done implies more work needs to be done so identifying defects is futile. Can you elaborate?
May
14
answered What are some effective ways of making scrum more dynamic earlier in a sprint?
Mar
18
comment Sprint pressure causes quality issues?
A great saying I have come across is this: "If you think your sprints are not long enough, shorten them" (attributed to Ken Schwaber, I think). I have not come across a product backlog item that could not be broken down into smaller items that can be consumed within a sprint. Yes, it may take effort. Yes. it may take knowledge. Yes, it may take experience. But it can be done. No-one said Scrum was easy. If you want to reap the benefits, you have to pay the cost of doing it well.
Mar
17
awarded  Commentator
Mar
17
comment How should we handle extra cosmetic features in Scrum sprints?
You'll be delighted to know that the latest version of the Scrum Guide (July 2013) no longer refers to shippable The phrase now used is potentially releasable.
Mar
16
revised UX designers working one Sprint ahead
deleted 30 characters in body
Mar
16
comment UX designers working one Sprint ahead
@BryanOakley I agree that some thought needs to be given to all work up-front, not just ux. However, the value of that work is decided by the stakeholders. If ux work is done one sprint ahead, the feedback loop has just been extended by at least one sprint. I would suggest that this is an unnecessary risk. UX is no different from design, or architecture, or database design, or report format. It CAN all be done in one sprint, with product backlog items that are created as vertical slices of functionality.
Mar
16
comment UX designers working one Sprint ahead
@Eugene In what sense are they on the same team? I would say that if they're working one sprint ahead, they're not on the same team. Incidentally, Scrum is also clear that it does not recognize "sub-teams" so again, I'd say that your situation doesn't sound like Scrum. Certainly not as I know it.
Mar
16
answered UX designers working one Sprint ahead
Mar
11
answered Scrum: relaxing “done” or using spikes?
Feb
21
answered Using Scrum on small projects where Owner doesn't want to be involved
Feb
4
comment Scrum: Writing the time it took to complete a task
@Eugene Mike says "A Scrum Master has authority over the process." A Sprint is part of the process, writing how long a task took is not. In my experience, good Scrum Masters never tell the Development Team what to do. They guide, mentor, coach, assist or facilitate but they never command, or direct.
Feb
3
comment Scrum: Writing the time it took to complete a task
@Eugene I can't see where Mike says that in the article. Perhaps you can point it out for me?
Feb
3
answered Scrum: Writing the time it took to complete a task