News for hackers. Stuff that matters.
Re:Implementing SCRUM - story of a Seedcamp winner by DanielBMarkham on Tuesday March 03, 2009 @11:04AM (#501523)
Great to hear a new Scrum convert and the difference it can make in a team! (startup or otherwise)

Couple of notes from an old Agile guy:

1) The Product Owner goes away with a startup. Everybody is representing the business. The P.O. idea was always an oversimplification anyway. In reality you have to adapt. (This is true of all of this)

2) You don't have to plan every task. Some teams do, some teams don't. Stories are hunks of business value that you can deliver inside a sprint. Tasks are what you do to make stories happen. If you can grab a story and deliver it, tested and approved, without decomposing your story into tasks? Good for you. I say go for it. But it's a team decision. Some folks are just more detail-oriented than I am. All I care about is getting the value to the customers.

3) It's a framework, not a methodology. Scrum is a PM framework around Agile principles. It doesn't tell you how to do things, simply the process for keeping track of your team's to-do list and executing on that list. It's all goodness and wondefulness, sure. But it's not the end of world hunger. Just some nice rituals to keep the team on-track.

4) The most important part of Scrum, or of agile for that matter, is to adapt. It's okay to totally screw-up. What I want to see is a team that is constantly improving their ability to deliver value. Whatever you read in a book or see in a seminar, you have to own and adapt it for your use. I've found that many folks get the idea of "process is evil" and then start to use cookie-cutter processes for their agile teams. Ouch. All of those rituals like stand-ups, showcases, retros and such? They're there because over time we believe that most software development teams will adapt to use some form of them. So start with them for a few cycles, then change it up.

5) Because of all of this, there is no conflict between Agile principles and startups. In fact, every startup I've seen that was successful was in some fashion agile. Startups are about providing perceived value to the customer quickly. Agile is about providing value to the Product Owner quickly. Unless you screw it up, it's the same difference.

If you haven't looked into it, I'd give some agile concepts a look-see. Even when I sole-developing I use a backlog, sprint, "done", etc. Not because I'm a fan, but because it is just the best way of working.

Re:Implementing SCRUM - story of a Seedcamp winner by vladimiroane on Tuesday March 03, 2009 @11:07AM (#501528)
True: it is framework not a methodology.My mistake.
Re:Implementing SCRUM - story of a Seedcamp winner by moe on Tuesday March 03, 2009 @12:19PM (#501636)
It's okay to totally screw-up.

Coincidentally the two times I have seen SCRUM at work so far it was deployed precisely to serve as excuse for the constant screw-up. Neither of the companies seems to have improved over that year of colored post-it notes either. But the CTO and product managers since then have new buzzwords they can use to justify why they still miss milestone after milestone...

YMMV.

Re:Implementing SCRUM - story of a Seedcamp winner by DanielBMarkham on Tuesday March 03, 2009 @12:52PM (#501673)
It's okay to screw up if you're continuing to improve. Sounds like these guys weren't.

I tell my PMs that I train that no, I do not want them to be the CSM. I want them to work strategically, to work on all of those organizational obstacles that get in the team's way. You can't change the world, but good agile teams are going to be constantly reminding the CTO and everybody else that certain constraints are killing team performance.

You can treat it like a fad if you want -- just throw new labels on old crap. But whether it's Scrum, Agile, or Bob's New Process, at the end of the day the teams must communicate back to the organization frequently about what's screwed up. And the organization must listen. Or you can just keep throwing money and fads at problems you won't acknowledge. Reality is reality. The reason you end up with poor understanding at the CTO level is because nobody has the balls to tell him what's really going on. That conversation is the toughest part of adapting in a nutshell (pun not intended).

Re:Implementing SCRUM - story of a Seedcamp winner by moe on Tuesday March 03, 2009 @03:26PM (#501914)
Well, I sure hope someone uses these processes as they are meant and as you describe. This was not aimed at you personally, I just have never witnessed it.

In fact the words "Agile", "XP" and "SCRUM" have pretty much turned into red flags for me. My immediate reflex whenever someone feels a need to mention those to me is to bill by the hour - because anything else would probably come back and haunt me iteratively ...

Re:Implementing SCRUM - story of a Seedcamp winner by DanielBMarkham on Friday March 06, 2009 @07:04AM (#505399)
I'd be careful of overgeneralizing.

Even in true management fads, there's usually a grain of truth in there somewhere.

Just don't be the guy who never picks up any new skills because 1) people usually misapply them, or 2) you had a bad experience. Everything is a tool in your toolbox. Lots of tools means lots of options.

I've found that even with "heavy" process overhead, like CMM or CMMI, if you talk to the developers they're supposed to be practical and make sense. It's the way people in companies apply these things that are usually at the heart of why they don't work. At the end of the day, it all gets back to people.