Archive for Planning
Why Just Enough Technology?
Posted by: | CommentsJust Enough Technology means providing the right technology to solve the right problem at the right cost. Not too much, not too little. The objectives of the business must be prioritized and kept in mind from concept to design to implementation to maintenance. Every decision made along the way must map to a business objective. Every software requirement must map to a business objective. This is the foundation of Just Enough Technology – clear and concise business objectives. Those objectives drive the requirements, and the requirements drive the design and implementation.
This is how I ended a short article about Just Enough Technology a while back. I’ve reproduced here for your reading pleasure. Differing opinions are invited 
Why Do We Need Software Architects?
Posted by: | CommentsAnother Blast From The Past Article – Originally Published in Sept. 2003
I am a software architect, but I’m not a “Blue Sky” thinker; I’m more of a practical thinker. I asked myself some questions about architects. What is a Software Architect and why do we need them? What do we expect from architects and why not just have a tech lead? Is there real benefit in an architect and are some projects too small for an architect? If so, what qualifies a project as needing an architect? Read More→
Choosing Between Java and .Net
Posted by: | CommentsAnother Blast From The Past Article – Originally Published in Oct. 2004
I’ve been going over some articles I wrote over the years and have resurrected a few for Just Enough Technology. They are interesting in that the ideas are (usually) still valid and relevant in today’s world. This article was the basis of my focus on .Net over the last 7 or 8 years. I’ve created significant applications in both Java and .Net, and I am a great believer in choosing the right technology for the job. That could be Java or .Net or something else. This article contains some tidbits of truth concerning selecting the best technology based on real criteria – that is, criteria that are based on solving a business problem, not an arbitrary preference. Read More→
Risk Management in Requisite Pro
Posted by: | CommentsRisk Management is an important part of project success. Here is one way to help perform Risk Management using Rational Requisite Pro. Risks are a part of every project. Successful projects successfully manage risks. You can never completely eliminate risk, so it must be dealt with proactively.
A Programmer’s Bill of Rights?
Posted by: | CommentsHere’s a link to good post that talks about how companies can enhance developer productivity with some small investments in things like dual monitors. I just reread this article after finding it over a year ago. I am diligently trying to move our own department towards the things listed in the article, though some items, such as dual monitors, may be difficult for us given the current economic climate. We developers understand experientially how these things help our productivity, but is not always easy to communicate these truths to management. Read More→
