Hot answers tagged management
13
While what you have done is sure to be a good thing, the project manager has to worry about a number of things:
testing - what if you break something. Either something in the home page, or some other unintended consequence? The system needs to be retested. Depending on how far your company goes, this could be a large cost.
Scheduling user downtime. May be ...
7
The core strategy here is to understand the incentives and motivations of all the other players in your ecosystem. Where a naive participant might assume that technical proficiency is the primary goal of an engineering organization, the reality is a bit different.
The key is this Upton Sinclair quote:
"It is difficult to get a man to understand ...
7
You said that the meetings feel like you are lecturing them. If it feels that way to you, and the team doesn't seem interested in what you have to say, then why still have the meeting? If you're just throwing information at them, and it isn't holding their attention, why not just summarize everything in a weekly email instead?
If you want to make use of ...
4
Well first and foremost, it has to pass all your regular Q/A steps AND show a real performance improvement.
Now you're faced with a business problem: the client has what they paid for. They've accepted it, and are using it in production. They think the project is finished.
It is possible that they don't want to risk 'rocking the boat' for an update that ...
4
Welcome to the world of middle management!
You are going to find this type of problem happening a LOT!
You have 3 options:
Big Stick
Do this or you are sacked - never works. Don't do it.
Ownership
Get them to facilitate the meetings. Take a step back and nominate someone else. Have it as a rotating position where a different person hosts each time.
...
2
Has the client approved the cache expiration period?
Have you run the same tests as for the last release against your
branch?
Will redeploying result in the site being unavailable? If yes, will the client provide a variance to your service level agreement regarding up-time?
If the answer to any of these is "No", then it isn't ready for deployment. If the ...
2
Typically one would refer to an in-between mini release as a patch. The line between a patch and a full software release however is not a settled matter by any stretch of the imagination. It is sometimes hard to make that determination.
How much development work went into the patch?
It is not always about how much development work went into the patch. A ...
2
Try giving the developers more value in your meetings. A few examples might be:
short demos showing new features developed in the recent sprint. (presented by everyone)
a lessons-learned discussion in which they have a chance to change the way the team work and improve (discussion led your right hand in the team, and you are there to justify your ...
1
Don't hold long meetings and leverage project managing software. If you want to keep people interested, then condense and highlight what matters and save the rest for project logs and reports. Concentrate on milestones, deliveries, highlights and goals, and if only applies to 1/3 of the people, shelf it for a project discussion thread.
Keep your meetings ...
Only top voted, non community-wiki answers of a minimum length are eligible
