Don't sweat the top down change. It's normal and happens all the time.

If you go into the process thinking it won't help, then it's already failed. Instead, go into thinking that there may be things that can help and create a better product in less time.

Don't try to implement everything Scrum all at once. Take one or two concepts from it that you think will help and implement those first. Don't be afraid to tweak things and adjust as you go. After 60-90 days, add something else in.

It may also help to talk to the boss and find out why he wants to move to Scrum. If it's because it's the latest buzz word, that's not good. You should talk to him about past experiences with trying to implement Scrum. Tell him your plans to start moving to it. Whatever you do, don't tell him "it won't work".

>Thanks. I plan on getting more training. I've read a lot online but seems training should help out a lot. I'm for the switch I just don't think we are going to get a big bang until we also add in test driven design. Our current QC takes over 600 hours to fully test a system release. Part of my resistant is pride in both I'm good at what I currently do (resit change) and I wasn't consulted in the switch pretty much just came top-down. I'm a big believer in build buy-in and not dictate. But since I do think it will be for the better I just need to try and move on :)