Hey Arthur Brownl of your above points you mentioned. As you told now working with a team of 9 members, you should start thinking in that way and need to mark few point:
- Involve all your team members for all possible discussion.
- Before pushing any process let them also to analyse whether proposed process is going to help or not.
- Always try to server scope is pieces or in very simple and smart way. Smart program managers are keen on managing a realistic scope. You should work closely with the parties involved and ‘squeeze out’ the ambiguity in the scope definition that ends up in contractual documents, project plans and schedules.
- Help team to understand the future of piece of code/function/release by pointing in the right direction by providing clarity. Let them to comeback with some plans to scale your features.
- You should also help them to do some experiment because this experiment will help all f your team members to learn hell alot.
- As a program manager you should not react as a robot. I agree, numbers are important, deadlines are important, and clients are important. But if that’s all you care about, you might as well just replace your heart with a battery pack.
- And finally you should always Train Your Team for Success and for this you should not do-follow up blindly, you should do some home work before this to express that tag line more effectively.