Author |
Topic: choice between development processes (Read 613 times) |
|
puzzlecracker
Senior Riddler
Men have become the tools of their tools
Gender: 
Posts: 319
|
 |
choice between development processes
« on: May 2nd, 2006, 7:00am » |
 Quote  Modify
|
Hello,
I am developing a product where time to market (strict deadline) and
costs are important. First version is to be delivered in six month
(and possibly earlier) from the beginning. We have five fairly
inexperienced (some recent grads) developers for this duration.
I am curious which model is ideal for this situation (why, how?). I am
considering the following models: waterfall, incremental, spiral and
prototyping.
Manager is a pretty experienced and programmatic.
What are you suggestion about development process model: cons, pros?
Sincerely,
Michael.
|
|
 IP Logged |
While we are postponing, life speeds by
|
|
|
SMQ
wu::riddles Moderator
Uberpuzzler
Gender:
Posts: 2084
|
|
Re: choice between development processes
« Reply #1 on: May 2nd, 2006, 10:01am » |
Quote Modify
|
I hate to say it, but speaking as someone else who programms for a living: you may be screwed. 
{ On Time, On Budget, On Spec ) -- pick any two.
As for development process:
- Communicaion is the most important part of the project, both between the team and the customer and between members of the team. Hold short meetings regularly rather than long meetings infrequently -- it gives everyone less time to go down a wrong path due to a misunderstanding or incorrect assumption.
- Requirements will change. Plan for it. Most customers don't actually know what they want in anything but the broadest terms. Sometimes they know what they don't want, but they usually don't even know that until they've used the product for a while.
- Get something in front of the customer as soon as possible. A customer that feels involved in the development process is much more likely to be forgiving of time and/or budget overruns.
- Developers tend to focus on functionality -- when you click the X button A, B, C and D will happen. Customers tend to focus on visuals -- screen Q will have an X button on it. The earlier in the process there's something for the customer to see -- even if none of the widgets actually do anything yet -- the happier they'll be.
I think that reasonably rules out "waterfall" -- and my understanding is that most of the industry agrees -- but which of the other formal development model best fits that scenario I don't know. I've always been the code monkey rather than the manager ... and I hope to keep it that way.
--SMQ
|
|
IP Logged |
--SMQ
|
|
|
Grimbal
wu::riddles Moderator
Uberpuzzler
Gender:
Posts: 7527
|
|
Re: choice between development processes
« Reply #2 on: May 8th, 2006, 8:30am » |
Quote Modify
|
on May 2nd, 2006, 10:01am, SMQ wrote:{ On Time, On Budget, On Spec ) -- pick any two.
|
|
on May 2nd, 2006, 7:00am, puzzlecracker wrote:I am developing a product where time to market (strict deadline) and
costs are important.
|
|
It seems you'll have to do without the specs... 
|
|
IP Logged |
|
|
|
|
RIDDLES SITE
WRITE MATH!
Home 
Help 
Search 
Members 
Login 
Register
Reply
Notify of replies
Send Topic
Print