If you had to pick the best artifact in scrum, what would it be?

Question

We are in the process of implemeting SCRUM, however, there's some resistence from managment, and I thought it'd be a good idea to start implementing some practices and add more incrementally, to avoid the initial rejection.

How do you suggest I start?

Answer 1

split up work in 8 hour tasks per developer, start with the daily status meeting

what did you do yesterday, what will you be doing today, what is blocking/stopping you from accomplishing your task for today

Answer 2

I started by taking a class from this guy:

http://www.mountaingoatsoftware.com

who wrote this book:

http://www.mountaingoatsoftware.com/book/1

It was a great way to start, and was well worth the cost of the class.

Answer 3

Start with a good, prioritized backlog of all known feature requests.

Answer 4

I have found the best thing about a SCRUM is that you get some visualization on what people are doing. This stops people going down a rabbit hole. Well, too far down a rabiit hole anyway. The act of having to express what you are doing gives you some clarity into your downward spiral.

Given that, just as SQLMenace suggested, start with a simple daily get together. It is simple and will get results.

Answer 5

I think one of the key selling points to management is the transparency of the process.

• Make your product backlog available to everyone.
• Get them along to listen in at the daily meetings
• Stick your burn down chart on the wall.

Basically make it clear how much easier it will be for them to find out the status of the work.

Answer 6

I was hired as a developer here at my new company and part of the reason was of my process management experience. I'm bringing some Scrum love into this shop. However, I'm meeting serious resistance from my fellow dev. She's not into any process and simply refuses to admit she's got problems.

However, the rest of the company (my boss, my product manager and me) love scrum and what it's doing to highlight where we are at in the development cycle.

I started out by doing everything on paper. Basically, I'm using a chart similar to what you'll find in this PDF by H. Knieberg - Scrum and XP from the Trenches.

We already have a bug tracking tool in use so a big step for me was to make sure everyone is using it in some standard way and added a few custom fields for customer priorities and iteration priorities, iteration names, etc. That's made a big difference.

My coworker will be forced to use scrum sooner or later and I'm not sure why she's so hesitant. Anyhow, I'll post a question on that soon myself.

Good luck,

beaudetious