Project Management

Please login or join to subscribe to this thread

How to bridge disciplinary gaps?

linkedin twitter facebook   Communications Management   Estimating   Schedule Management   Scheduling  
avatar
Sonali Malu Maharashtra, India
There are few team members in the team who do not respect timelines. They work in their own schedule, do not perform unit testing. So if a bug is resolved, other 2 bugs are opened. And when ever management cross question about this, then just blame to requirements or poor schedule - even if requirements accepted and estimated by the team in first place.
Any suggestions on how to resolve such disciplinary gaps?
Sort By:
< 1 2 >
avatar
Sonali Malu Maharashtra, India
Dec 13, 2018 11:53 PM
Replying to Anton Oosthuizen
...
Sonali, I would venture to say that the problem stems from a lack of communication. I've seen in many organization that requirements would be documented and given to the dev team without any discussion (I'm not going to jump on the agile wagon). Typically in these situations estimations were given on best guess and sometime just to get the monkey of my back. In reality however the task might take much longer due to complexity not understood, missing details etc. When they then try to make a deadline under pressure the result is sloppy work and missed deadlines.

So before I look at how to resolve discipline I would try and identify the cause. BTW you might already have done this?
Yes, RCA is done for multiple releases and always found the same cause like under-estimation, no time for req management, etc.
Analysis performed by team and also provided estimates. We decide release date by adding buffer on top of it. Still, the result is always same.. Delayed release and feature takes lot of time for stabilization.
avatar
Sonali Malu Maharashtra, India
Dec 15, 2018 7:08 PM
Replying to Adrian Carlogea
...
It is not the job of the PM to "discipline" employees this is the responsibility of the functional manager. In the majority of cases the software developers and the software developing project managers are at the organizational level peers which means that the PMs don't have the authority to discipline developers.

Software development is a creative activity and because of this, unless we are talking about trivial tasks, it is impossible to give accurate estimates. Also bugs are inevitable no matter how many unit tests you are writing. Probably Microsoft developers do write unit tests but ever since the release cycle for Windows has moved to 6 months the system has had a series of sever bugs. It is much worse than previous systems that had a much longer release cycle.

In some cases developers do have to be disciplined if they don't perform their job properly but missing dead-lines or producing many bugs is not a criteria for determining that the developers are negligent. You need managers with technical background in software development to determine this or other mechanisms that exclude the opinions of the people that have never written a line of code in their lives.

You need to get your hands dirty in software development and get to a reasonably good level before you can understand these things.
True, I guess a technical head is needed for the team to review coding practices and to monitor their time as well.
avatar
Sonali Malu Maharashtra, India
Dec 14, 2018 7:04 AM
Replying to Bala Sripada
...
I agree with Ajay here in a way.

That being said, you can ask EOD status by sharp 6 PM or so and basing on that, you can pose questions to them.

When I asked status in a company where I was working, they said, earlier managers( before me) never asked!!!. I told them that till I get a better handle, I needed it. So it took couple months.
Also tried this micro management in few ways. But they'll make an excuse and leave, actually don't respect timelines and don't own the deliverable.
avatar
sandeep Madavi Manager| Cape Plc Dubai, Uae, United Arab Emirates
Hi Sonali, how did this go? did you manage to get the situation Improved? do you have some learnings to share?
avatar
Stéphane Parent Self Employed / Semi-retired| Leader Maker Prince Edward Island, Canada
I live by the motto: "Trust but verify!" That means, I believe that the project team members have the best of intentions. However, I make sure to confirm that what they said they did was done and done right. Some of it you might be able to do yourself. The rest you will need someone like a team lead or senior developer to do the review.
< 1 2 >

Please login or join to reply

Content ID:
ADVERTISEMENTS

I hate asking for change. They always make a face. It's like asking them to donate a kidney.

- George Costanza

ADVERTISEMENT

Sponsors