PHP Developers Network
http://forums.devnetwork.net/

Developer Accountability
http://forums.devnetwork.net/viewtopic.php?f=36&t=137406
Page 1 of 2

Author:  Benjamin [ Fri Feb 15, 2013 2:19 pm ]
Post subject:  Developer Accountability

Typically I pay developers hourly. Sometimes I get one that double bills, that's pretty easy to spot so I just get rid of them.

One of my clients wants to setup an in-house development team. He wants them to work 9 to 5 so he can make sure they are working for the hours they are paid.

I told him this won't really work because developers do their best work on their own schedule. That's one reason at least.

Anyway, what are some best practices for an employer to ensure they are getting what they are paying for, without a rigid schedule?

Author:  Christopher [ Fri Feb 15, 2013 3:00 pm ]
Post subject:  Re: Developer Accountability


Author:  Benjamin [ Fri Feb 15, 2013 8:56 pm ]
Post subject:  Re: Developer Accountability

Well this is for employees he wants to hire. He wants to make sure they are working all the hours they are assigned, e.g. they actually worked 40 hours in a particular week.

Author:  mecha_godzilla [ Fri Feb 15, 2013 9:32 pm ]
Post subject:  Re: Developer Accountability

If I can just add a couple of points here, it would be a good idea for the client if they have regular weekly catch-up meetings with their developers to gauge progress right from the start of the project - being able to demonstrate what they've done in that particular week in a practical way increases the likelihood of them actually doing and achieving something, and the team gets "buy-in" in on every aspect of the project. If the code isn't ready, let the developers know that's fine - just demonstrate what they've got and point out what's missing. The important thing is to keep it informal and productive i.e. minimal preparation and no "where the hell is that search function you said would be ready?" attitude.

There's no real way to guarantee that the client's developers will be working a 40 hour week - yes, they may be sitting in an office starting at a screen for those 40 hours, but are they being productive? Personally, I find keeping a development log and just recording a start/end time for that particular activity is fairly quick and easy to do and is far less onerous than having to account for every 15 minutes of the working day. If I had a manager standing behind me, asking what I was doing every 5 minutes and telling me which buttons to press, that would be the end of that job for me.

Lastly, isn't it results that count? What happened to "working smarter, not harder"? :) I know there's always the potential for people to abuse the system, but that tends to happen when the respect has gone - which is almost always down to poor communication between the two parties or some other kind of grievance that arose at an early stage in the relationship.

M_G

Author:  Christopher [ Fri Feb 15, 2013 11:43 pm ]
Post subject:  Re: Developer Accountability


Author:  Benjamin [ Sat Feb 16, 2013 12:03 am ]
Post subject:  Re: Developer Accountability

Ok, so what's the best solution to make him feel comfortable that he isn't paying for time that isn't producing results?

Author:  Christopher [ Sat Feb 16, 2013 12:07 am ]
Post subject:  Re: Developer Accountability

Ultimately he needs to put a budget amount on each deliverable. From that he can start to get a sense of actual productivity. But I think he will have to prove it to himself ... but you can say that to him in another way.

Author:  Benjamin [ Sat Feb 16, 2013 12:12 am ]
Post subject:  Re: Developer Accountability

That's a tough one. The software is 90% complete, but was developed by an outsourcing firm so there's major components that need to be refactored-reengineered. He doesn't know how long certain things take. There needs to be a certain level of trust here. I'm just trying to get him setup with policies and procedures that ensure quality and give him peace of mind.

Author:  Christopher [ Sat Feb 16, 2013 12:17 am ]
Post subject:  Re: Developer Accountability

Has he done any software development management before? Or was he just product managing the ousourced work? I think I would recommend he bone-up on Agile management. Maybe something like this: http://www.amazon.com/Agile-Project-Man ... 073561993X

Either he needs to jump with both feet, or hire someone like you do manage development. Holding programmers feet to the fire 9-5 is a pretty bleak approach. But if he and the programmers are all neophytes then it's not the worst plan. If they are more skilled then it sounds bad.

Author:  Benjamin [ Sat Feb 16, 2013 12:20 am ]
Post subject:  Re: Developer Accountability

He's the owner/investor with minimal software development/management experience, although he does have management experience in other areas. I'll check out the book. I'm thinking probably he should just have everyone log hours and cross reference time spent with deliverables maybe?

Author:  Christopher [ Sat Feb 16, 2013 12:26 am ]
Post subject:  Re: Developer Accountability


Author:  Benjamin [ Sat Feb 16, 2013 12:29 am ]
Post subject:  Re: Developer Accountability

Yeah that's an issue we encountered, where the policies he intended to drive/monitor production were having a negative impact. Let me know if you think of anything else, I'll draft up a plan for him based on the comments here.

Author:  Christopher [ Sat Feb 16, 2013 11:28 am ]
Post subject:  Re: Developer Accountability

This is mini laboratory for doing software development right. I think the most important things to instill are: group development, no individual ownership of parts of the code, code reviews and even some pair programming, unit testing, doing real design work in those 2 of 6 hours a day spent not coding.

Author:  Eric! [ Sat Feb 16, 2013 4:36 pm ]
Post subject:  Re: Developer Accountability

It's possible that you don't have a productivity problem at all. Can you extract some per-person metrics from your VCS? Just to get a gauge? It's complicated because it may work for requirement changes or tweaks, but it might be a starting point before having to make everyone track their hours, which they would probably fudge some anyway.

Author:  Christopher [ Sat Feb 16, 2013 6:49 pm ]
Post subject:  Re: Developer Accountability


Page 1 of 2 All times are UTC - 5 hours
Powered by phpBB® Forum Software © phpBB Group
http://www.phpbb.com/