Question

First a little about myself. I am not an experienced software engineer, architect or developer. I have done mostly small ASP and ASP.NET projects in C# for the last 5 years. I am pretty good with HTML and JavaScript. These projects were done when I had free time from my other duties which were not related to software development. I have now been moved into a software developer position. The company I work for is not a software development firm.

I am now working on a Silverlight LOB application with WCF and Entity Framework. I have been given little specifications for this project, just the ‘make an application like X, only simpler so we don’t have to pay for it’, my boss doesn’t check on my progress as often as I think he should, the project manager(a co-worker) will stop by now and then but we never discuss the specs, architecture, UI or business rules. I am mostly just asked when I think it will be done. I have had to learn Silverlight, WCF and Entity Framework to work on this project which is not a problem as I really enjoy working with these technologies. The problem is I am the only one in the company that knows anything about these and have no mentor/boss to discuss the problems and how they could be solved. I have been able to seek out one interested party in the company that has at least given me a list of some of the requirements.

I can’t believe this is how software development should be done. I think the project managers should offer guidance and keep a closer eye on what is being done to prevent going in the wrong direction(but how can they in my situation since the don’t know the technologies!).

Should I feel this way or am I way off base?

Thanks for listening.

Answer 1

Every organization is different. If they are operating in this capacity then you should adapt and make the best of the situation. It’s either happening because that’s how things are done and they are aware of it, or they don’t know the wiser or don’t want to invest to improve the process of delivering strategic/tactical projects.

In a perfect world everyone would have a robust Quality Methodology in place which would provide a framework for Project delivery and systems implementation. It’s just not a reality.

Here are some tips to help you operate more effectively:

• Identify your sponsors (the people who own the product) and determine the high level benefits and driving objectives of the business problem they seek to solve
• Identify your stakeholders (who has influence and who has interest) and get them to communicate their needs as much as possible
• Involve both sponsors and stakeholders in the process as much as possible or as much as they want
• Capture what requirements you can from them through written form (email)
• Provide opportunities for them to gain visibility into the delivery and to provide feedback