Unless you are a micro-manager yourself, you won't experience that big of a change. You will still assign projects but those projects will more often be a SCRUM team project instead of an individual project. Even individual projects can still benefit from the SCRUM process. They all have similar events that take place (code review and testing, etc). You will be able to see the individual participation and accomplishment more easily when you look at the PBIs and SBIs. Each developer takes on an item and you as a manager, could go look at the difficulty of the item, the code for the item, the interaction with 3rd parties required for that item, the resulting function, etc. One thing you might want to consider as a manager is to ensure that you use a tool (whatever you decide it will be) to enter and track the entire process - especially PBIs and SBIs. Also request that each team member (I'm referring to developers) enter their daily SCRUM comments as a daily log that you can view (hopefully in the same tool). Since the meetings are kept short, it should take no more than 5 minutes for your developers to do that and should be detailed. Since you will not be able to attend every SCRUM meeting (and shouldn't but you may want to sit in and observe SCRUMs everyday perhaps rotating which one you go to), you will see what each person has on their plate for the day and what they accomplished the previous day.






>The top-down change is just sticking in my craw. Before the new president no change to my department or SDLC happened without running it by me. New president, new rules I guess. Still doesn't mean I have to like it :)
>
>
>>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 :)