Next steps in Scrum adoption?
- Hello all,I've written recently about recent steps I'd taken at a company I just joined on Feb 16th.It's been two months now and there is steady progress.We watched Jeff Sutherland's retrospective about Google AdWords.Next, we watched Mike Cohn about Agile Estimation and Planning.This spurred the other two engineers to want to give Scrum a try, so we got a Product Backlog filled up, then size-estimated it playing Planning Poker.Last week we set out to define a real sprint, pulling from the backog. It became apparenty early that each "feature" was going to need more requirements defined, design, unit-testing, and QA in order to be complete. These seemed to work out to a nice way of introducing the idea of "A Definition of Done", which was very much lacking before.This is all well and good. We even created a team-shared Task Board in the lead developer's office, which will replace the solo task board I had in my own office.The issue now, though, is that this is really surfacing problems in the current approach. There was an arbitary date for a full delivery of a rewritten system picked for July, and it's become apparent that this is not going to happen. What's more, there has been no QA done on this sytem at all. Things have been developed in part, in mass, and now we're supposed to "come back over" the apps and start tying parts together and we're supposed to have a QA person visit our office (he works up north) for a few days.This lack of QA and a lack of user and product owner involvement worries me most now.However, there is some more positive news.One of our sales leads saw Jeff Sutherland's traing book on my coworker's desk and started asking him about it, trying to figure out what's up with all the sticky notes. He explained very well the "big bang all at once" approach and the iterative & incremental approach relying on user feedback and product owner involvement. He explained about estimating size and deriving duration, and about measuring velocity over iterations as a way to introduce predicitability and repeatability.The sales lead was tracking with him and was very interested to help "test drive" the new application whenever we're ready for him to start using it.He is also the company owner's son, so hopefully some good words will flow up.In a situation like this, what would you do next?I'd like for him and others to, perhaps, read some things about Scrum and Agile, or watch some presentations.He's technical enough that he might benefit and understand the first few chapters of Scrum and XP From the Trenches.Whether or not he reads anything, I think a picture can convey a lot. So, I'll probably encourage my teammate to print some pictures of the Scrum workflow from wikipedia or Ken Schwaber's site. This will probably be the most effective communication vehicle at this point.,I think we really have a grat opportunity to do some incredible improvements on this company's systems and I'm hoping this approach will make sense more than the current waterfall-all-at-once approach is shaping up to be.Take care,Josh
- --- In email@example.com, Joshua Gough <jsgough@...> wrote:
> In a situation like this, what would you do next?I have a feeling you know better than any of us could from an
email message (especially with our tendencies to misunderstand
things on these discussion groups). You're live in the situation,
and everything you've done so far makes sense.
One thing that's helped me in similar situations is to invite
stakeholders to the Sprint Review Meetings. Once everyone
sees the car is moving, you might get a Product Owner to
jump into the driver's seat.
- +1 to this.
> I have a feeling you know better than any of us could from anemail message. You're live in the situation, and everything you've done so far makes sense.