Firstly, don't sweat it. It's never easy making the move from managing yourself to managing others. There's no magic formula to being a good manager but a couple of things that will help are: Be honest with people and don't bottle things up (that's when it becomes personal rather than business) If someone isn't pulling their weight take them aside and let them know it. Then work with them to resolve any blockers to their progress and between the two of you come up with a plan to get back on track. Make everyone aware of their responsibilities. Although you need to manage them, they are responsible for their own work and they should feed back to you exactly how it's going (a potted version of this is usually enough to cover your progress report to management). If you have people on the team who are under-utilised, make use of them. Give them a little more responsibility, something like putting together progress reports or doing some resource planning. They will usually appreciate you having faith in their abilities. Although you can still have a bit of fun with the team (and sometimes humour does help) it's important to remember that you still need to be impartial so don't get dragged into petty squabbles. It's also handy if you can get yourself some kind of coach to help you work through the tougher times and help maintain your sanity (I found a coach to be so helpful, I started doing it myself). Coaching is also an easy thing to pick up the basics of, and can be used with your team. It gets away from the bitching and whining and works on the issue. If time is short, invest in one of the DK Essential Manager Manuals. This gives a potted summary of all aspects of management and can get you off to a quick start. Although it's quite a thick book, it doesn't go into too much detail and you can dip in and out of it. I hope this helps and things start going smoother. :)

It seems like the team is still getting used to the SCRUM mentality but as with most projects, there's probably little time to waste on them getting up to speed. In reply to your original complaints and a couple of things that will help the scrum run better are: 1. Would any self organizing team of developers actually plan to meet every day? A. Yes, the team need to meet everyday so they are fully aware of where they are in the development process and where their team mates are. They need to be made fully aware (usually by the scrum master) of what each meeting will focus on and what is expected of them. 2. About half of the 15 minute morning morning consists of, "Lets have a Meet After to Discuss". Half the team stays after the meeting every day. How about just discussing it now and getting it over with? A. If they are having to have follow on meetings from the scrum, these should be formalised so that the results of the meetings can be shared at the next day's scrum. This will make sure that everyone is fully aware of any potential issues that could impact on their work and as they will have to put more into it than just chat for a while they will probably cut down on the amount of "discussions". 3. The other half of our 15 minute morning meetings is just to state that the status hasn't changed from yesterday A. This needs to be addressed, if there is no progress from one scrum to the next then the project is essentially stalled. If they are saying nothing has changed since yesterday then challenge them on why there is no change and what they are doing to address this. Whatever you do don't let this carry on. It is counter productive and other team members will start to get the impression that they are either doing all the work when others aren't pulling their weight or they will take it as the norm and just stop making progress on their part. From experience the simplest way to keep a scrum going is: 1. Give an update of where the project is along with any priorities. 2. Each person says what they accomplished yesterday and what they will accomplish today. 3. Everyone has a say and they need to question or comment on anything they don't understand or agree with. 4. The scrum leader has to keep the scrum as short as possible but at the same time covering everything that needs to be discussed. If the team is large, make certain people responsible for giving the updates rather than everyone chipping in. 5. Make sure that you thank everyone for their work and contribution to the scrum.