42
Conversation is Not Inherently Disruptive
I work with a team of developers who are talented but often distract each other with chit-chat.
You say they are "talented but distracted." What makes you think they are talented? Why do you think they are distracted? What is your metric for determining that the team or the process is operating at a sub-optimal ...
26
It sounds like you have team members from high power distance cultures. People may not speak up when the boss is in the room because their values require them to listen and follow, not to advise or lead. You may even notice it happening between junior and senior team members or between yourself and team members. Read more about power distance here: https://...
23
compare to other colleagues and feel insulted.
The other two answers are good - but this confuses me. When I've done stakeholder analysis, the process has been open and participatory. There shouldn't be any value judgement. Power and influence are closely related to budget and participation. If a given stakeholder feels that the graph shows them as less ...
22
No, don't even think about taking someone's phone. If they're looking at their Facebook account or personal Twitter account during a meeting, then you have a bigger problem, and the solution most likely would involve possibly trying to recruit and hire the right kind of people; ideally, those who are capable of acting like adults.
However, one thing ...
22
I think Retrospective is more appropriate name in this case
Imho, project is dead when it has been aborted (or abandoned), if it has been successfully deployed then the project is very much alive (the code is there and it works!).
21
1.How to communicate with them so they can be follow my instructions?
The team shouldn't be following your instructions, they should be following a plan that they contributed to and signed off on. As a PM your job isn't to do or manage technical work, it is to make sure that the people who are responsible for the doing and managing are following the plan.
...
18
that's a very pertinent question! I'd rephrase it in a slightly different way:
Why people don't pay enough attention to meetings?
The usage of mobiles (or any other gadgets) just for distraction (at least in the meetings I've been to) is mainly because people don't believe the meeting is useful.
So, instead of trying to solve the consequence, I'd suggest ...
15
Person-month is politically correct synonym for Man-month.
It's mean amount of work performed by the average worker in one month.
So, if:
project requires 12 persons-months of development time
all team members do only pure development activity (i.e. they are telepaths and they don't need to spend time for communication with each other). [note: this is not ...
15
I personally don’t like tools you have to hide. This leads to mistrust and if it leaks (for whatever reason) you are in trouble.
So we started 20 years ago to use a technique which is called project environment analysis (AKA extended stakeholder analysis). The tool is simple and efficient and is part of the open accessible project handbook and is also used ...
15
Analysis
There is a chilling effect when he is here. Am I overreacting? Should I just try to build up the confidence of the team? or should I ban my boss from the retrospective?
In my experience, this is a classic case of missing the forest for the trees, and mistaking process problems for interpersonal ones. Let's enumerate some of the issues that ...
14
When I was a new project manager, I had trouble separating my previous role as a developer from my new role as a project manager. What compounded my problem was that it was a gradual move, as the project I worked on started out as just me as a developer, and eventually led to me working as a project manager and leaving the technical details to the team.
...
14
You are actually in an enviable position in that you have a client who is engaged enough to get involved. My problem is usually one of getting that kind of attention.
Depending on the complexity of the documents and the size of the team you are probably saving more time (outside of travel) going through this FTF than dealing with it through email because:
...
13
Duck
First, introduce the equivalent of a stuffed duck in the office. Questions should always be asked to it first. This one depends on the level of trust you have from that other team, and their own technical level. Make sure they don't take it as poking fun at them for not being able to work on their own.
Question ticket board
Then, introduce a question ...
12
As Thomas Owens noted, one of the solutions to scaling up Scrum is the Scrum of Scrums. What you describe in the OP, however, is different:
We've tried that each team delegates an "ambassador" who participate on the others' stand-up too but in that case the info flow was not the best.
Instead of each team sending an ambassador to other teams' daily Scrum,...
11
Command-and-Control vs. Self-Organizing Teams
Should I collect all the phones before a meeting? ...I don't want to punish everyone just because a few people can't pay attention[.]
It depends. Are you facilitating a meeting between adults, or babysitting kids? If you treat adults like kids, then you abandon all hope of creating teams where people step up ...
11
The Problems
Reading between the lines a bit, it would seem that you have a few related issues.
Your "team" is too large to be truly agile. You may want to consider splitting up into cross-functional tiger teams with a focus rather than a multi-project, matrixed organization.
The purpose of your stand-up hasn't really been defined. Truly agile stand-ups ...
10
Great answers before mine!
Let me add this: I see the biggest driver to your schedule woes is feature creep. If you focus on nothing else, focus on this. When features are added like this, you get a new timeline against which to measure your schedule performance. If you are not enforcing an appropriate change process, then being on time is near ...
10
Redefine the Problem
You list several problems that you believe make your projects late. Specifically, you said that:
Deadlines are missed because we're adding many functions in that Web application.
We have people with not-so-good skills for that project.
The people who are freelancers will only have a little time to work.
These may be ...
10
Every industry has lingo. It slowly evolves and becomes a sort of sub culture of the industry itself. Even if technically not correct in terms of a literal definition or even proper grammer, it becomes okay and common and accepted.
So, no matter how any of us dissect the word, I doubt any of us can say we have never heard anyone use post mortem in our ...
10
option 1: it might work if you make these standups extremely quick and efficient (15 min is the maximum, standup could be much shorter)
option 2: sounds like a disaster to me; having so many people and projects, it would be impossible to process it all in a meaningful way and still keep it under 15 minutes; you might end up with long boring "standups" (I've ...
10
I don't know why aclear16 deleted his answer. His answer is perfect. There are a ton of positives with idle, unproductive time by way of teaming. It matures the team and you want that. I'd even go as far to say that, if you are running behind, let the social time continue because the positive aspects of that will help, not hurt. And likely the down time was ...
10
Great project management is not about hitting your targets 100% of the time. Much of our performance is probabilistic where many of the drivers of our results are out of control and very random. Missing your targets becomes a problem if it became a surprise for you as the PM and your customer. If you were monitoring properly, such as using critical path ...
10
Your Capacity Planning and Prioritization Processes Need Re-Engineering
You appear to be attempting to solve the wrong problem by treating this as an individual-availability issue. This is most likely because you have a weirdly-matrixed organization that isn't based around project teams or team capacity planning, but apparently based on the notoriously ...
9
The easy solution is to have only one standup which is for the team. My recommendation is to talk about only the upcoming work and focus on those issues which my cause some troubles later on such as cross-project tasks, integration tasks, tasks which are on the board for a long time.
With this approach the three personal oriented questions need to be ...
9
The downsides that you mention could just as easily be applied to project teams if you continue to have different groups siloed.
It's a threat to productivity and to project success as you can't ask peers from other functional units that you have to interact with a quick question without walking down the hall
It's a hit to project team morale as both teams ...
8
Prioritize, prioritize, prioritize.
One month could be considered a very long time, or a very short time for such a project -- depending on the scope.
So take the scope (ie. "features"), and list items according how their importance.
Start at the beginning. Do one thing at once.
This sounds obvious, but oftentimes developers will start "a little bit of ...
8
It is not subjective at all. It is the result of your stakeholder analysis, a necessary analysis that feeds your communication plans, your training plans, your stakeholder participation plans, and likely many other things. It is one of the most important things you do for your project and this is not an area where you want to go on the cheap or try to save ...
8
The first issue you must face: Are distractions good or bad? I think this can not be answered with either a clear yes or no.
First, no developer can work 8h on end and still remain sane. On a good day you get 4-6h of concentrated work. But don't think that, since they are not sitting concentrated at their desk that they are "not doing work". In my ...
8
Quick answer: It depends.
It depends on:
Frequency: If you're having a daily meeting, sending the minutes one day later make it useless.
Action Points: If you're dealing with several people that will follow the actions discussed during the meeting, better sending the minutes before having the other people doing anything. Otherwise, if the attendees carry ...
8
I recommend:
Demonstrate your application to the customer often, and get feedback early.
Break stuff down into small tasks that you are very confident about estimating time for. This is key.
Focus on minimal functionality first - login, logout, visit home page, etc. before the real features.
Use an Agile methodology.
Talk to your client daily.
Use software ...
Only top voted, non community-wiki answers of a minimum length are eligible
