When I was serving in the Navy, I had a CO who liked to be informed of everything that is happening on the ship. Cause it's his ship and he should be in the know for what happens around. And on a ship there are many departments like engineering, electronics, navigation and so on, and all these department has to coordinate with people all round, inside the ship as well as departments outside the ship so you can see it's quite hard for him to be on top of everything. If something happens and he is not informed, he is not too pleased especially if the information came from some other source. So the people on the ship developed a habit to always inform the CO of what's happening around the ship, to always keep him "in the loop" so to speak. He will offer his advice and even help to resolve some of the issues.
Now trying to keep up with what's going on in a software project is similarly just as hard as on a ship. There are so many components that make up the project and there are co-ordination between people from QA , procurement and even other project teams that you are interfacing with. The project lead/manager will be the person that management will most likely ask on a regular basis what's happening to the project. They might use things like monthly reports to update management to keep track of the progress, issues and so on.
Now what happens when management gets uncomfortable about the project, most likely management do some or all of the below
- More meetings
- From monthly to weekly reports
- In extreme cases even bother the developers to give him reports on what they are doing
No comments:
Post a Comment