The first shift required is a change in orientation from prevention to fast response. Many problems are catastrophic only if allowed to fester. Imagine you hear from an engineer that they are worried that a certain payment subsystem is unreliable, and will therefore double-charge some customers. One way to evaluate this fear is to spend time on analysis: how many customers will be affected? What is the maximum amount of overcharging that will happen? How upset will those customers be? How much will it cost to solve this problem now? In this framework, we’ll tend to either invest in the proposed prevention or do nothing.
(Link: The curse of prevention – Lessons Learned)
Archive | scoping RSS feed for this section
The curse of prevention – Lessons Learned
April 8, 2010
0 Comments
20% more bugs? Or 20% less features?
April 7, 2010
0 Comments
People often make the argument that time to market is more important that quality. I’m not sure just what they mean by that. Do they mean that it’s ok if 20% of the features don’t work so long as they deliver quickly? If so, that’s just stupid. Why not develop 20% fewer features, and develop them well. It seems to me that choosing which 20% you are not going to develop and then choosing to develop the other 80% to a high standard of quality is a better management decision than telling the developers to work sloppily.
(Link: 20% more bugs? Or 20% less features?)
F|R: How to Avoid Feature Creep with Your Software Apps
September 2, 2009
0 Comments
1. The Vision/Mission Statement Test
2. The Audience Test
3. The Scope Test
4. The Best Solution Test
5. The Revenue Test
6. The Attraction/Retention Test
(Link: F|R: How to Avoid Feature Creep with Your Software Apps)
The Web Design Process Start to Finish
August 20, 2009
0 Comments
The first thing that happens when I get an enquiry is I send the potential client a website planner. The website planner, a series of questions I have listed in a Word document, will gather requirements for the project.
The key objectives of the planner:
* Find out who the client is and what they do
* Who their target market/user is
* Who their competition is
* What deliverables they want from me
* Timeframe and budget
In a nutshell, NGD require a makeover with a modern & easy to use interface. I am responsible for the XHTML/CSS templates for the main pages (they already have a development team in place for the back-end programming & intagration).
(Link: The Web Design Process Start to Finish)
