Discussion Locked

In Small new org-start formal proj. mgmt

0 helpful
3 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

HOw does one go about implemeting formal software development processes when developers are used to work in traditional not so process oriented way.

People are not aware and have not tried it also - so there is lot of resistance to do it in a formalized way due to commitment to produce things in time and that someone is now going to check the quality too. So fear of failing to meet commitments.

What are practical tips to such situation so things do not backfire while trying to do good to everyone.

Is forcing things on people good in such cases or try to buy them into it?
Should they be given chance to expirement or not?
Can chance given to them be considered as failure to assert? Whats general psyche of the people working in such organization? and it best can be handled to implement formal agreeable processes?

I would like to hear from experienced people who have gone thru this situation and how they did what which may or may not have worked but that also would tell me what not to do.

Thanks guys.

3 replies

by 24hrs

Have you a formalized process that is documented? If not, get that done first. If you have, try it out on a small project as any change agent would recommend. It took me 3 years to put the methodology into those thick skulls of my engineers. Now, it has become a part of them.

by gbraches

The best way to gain acceptance is to show how it will make their job easier. We had a similar problem here. There was no defined build machine, developers were working from home and there was absolutely no build control. We got them on Star Team and made one developer the administrator with the QA manager acting as a facilitator. The QA manager monitored their progress for several weeks until he was confident that the process was being followed. Acceptance came the first time a change was required on a previously released build. In the past, changes of this type were chaotic, to say the least. Once the developers saw how easy it made the task they totally accepted the process and even improved upon it by saving off the development environment that the code was created with as well.

by jamesrl

Start slowly.

The easiest way to make this fail is to come at the team with over-burdening bureaucracy that doesn't add any value.

Focus on finding a problem that a formal methodology might help address. Look for some simple processes that might help sort it out.

You need support from management. You need buy in from staff. You need to let people know that this isn't a project to implement a process, but an ongoing living process of creating, then enhancing the formal process - its a living thing that needs to be flexible to change to suit the needs of the group. Keep thinking of added value.

James

This discussion is closed to new replies.