Scenario: I've tasked a developer with creating a login form, and there are no dependencies for this assignment. However, the developer is taking longer than initially estimated. As a project manager, what steps can I take to prevent such delays? Saving Changes...
The first question is whether it is something even worth worrying about. Tasks with no dependencies are a gift to the PM. If nothing is waiting on the task, it can be completed anytime during the project. The risk is how much it costs to complete.
On the other hand, I have certainly seen team members milking a task for all it is worth and it justifies why we keep track. I would talk to the employee and ask how you can help. "I noticed this task is taking significantly longer than planned..." That shows them that you noticed, without being adversarial. Was the estimate too optimistic? Are there roadblocks you can remove? Do they have competing priorities so they can only work on the task part time? Is there any other help you can provide?
Sometimes shining a light on the problem encourages others to fix the problem before it escalates.br type="_moz" Saving Changes...
Senior Projects Manager | Field & Marten AssociatesNew Westminster, British Columbia, Canada
Jobby, I do agree with Keith's feedback and insights. I would first check with the developer and see why are they running behind. Maybe this requirement changed from a Must Have to a Should Have for this iteration and they will tackle it in the next iteration so the first step would be to understand the reasons behind falling back and then if you, as the PM, believe that the priority should be different, you can discuss with the developer and reprioritize it in the Product Backlog. Saving Changes...
George FreemanThought Leader | Author | Architect| Florida, United States
Joby,
Pre-plumbed technical accountability events, such as:
1. Twice-a-week technical reviews where developers provide verbal and visual updates (e.g., team screen sharing) of their development efforts to the development team, wherein they understand that the team dynamically challenges each other (in the review) to benefit the project and each other’s efforts.
2. Technical mentorship relationships where all developers expect their mentors/leads to check in with them periodically (note: on an unscheduled basis).
I’ve been in the software development business for over forty years. Although developers may initially push back when they see accountability structures like this, they eventually appreciate it as they learn that a “challenge-based” environment is healthy and promotes their professional interests.
Anything short of a challenge-based environment will leave a project manager without a rudder to steer the ship. Saving Changes...
Keith, Rami & George have provided valuable feedback. My take is somewhat complementary - how are there NO dependencies for this functionality? If so, what value does it bring to the system as a whole? At a minimum, you would expect dependencies on non-technical deliverables such as a user guide, help desk support scripts and so on.
Kiron Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Software is a totally different and special discipline than others. Why? Because a software attribute called "intangibility". But not matter software or not the key is be aware of impediments that people can call risk and issues. Saving Changes...
Community Champion
