Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
?
Solved

How rigid is your design specification?

Posted on 2014-10-05
2
Medium Priority
?
274 Views
Last Modified: 2014-10-15
At the start of any major project there is typically a design specification.  As the project progresses new requirements naturally emerge. My questions are,

Once the original design specification is determined how rigid do you or your team adhere to that spec.?

How do you manage the balance between time to market and the never ending release date?

And where do you draw the line on changes that are significant to a customers needs and version x wish list items?

Thanks,
Ron
0
Comment
Question by:rwensley
2 Comments
 
LVL 37

Accepted Solution

by:
TommySzalapski earned 2000 total points
ID: 40364041
There's obviously a balance. You can be too rigid, or too flexible. I would say that if the change is feature based ("hey, we could add this feature while we're here"), reject it. If you found something while implementing that changes what the "right way" is, then consider it.

There will ALWAYS be some other feature or wish list item that you could squeeze in "without much extra effort." Be strict.

However, if it's a question of doing things right the first time (and perhaps taking a bit longer), do it that way. Do not sacrifice code health, good tests, or scalable design to meet deadlines.

So when you make a design, pick the features you will implement in the first phase, hold firm to that list, and then take the time to make those features work right.
0
 

Author Closing Comment

by:rwensley
ID: 40383347
Sorry for the delay I was out of country.  Your answer was along the lines of my point of view.
0

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

"Disruption" is the most feared word for C-level executives these days. They agonize over their industry being disturbed by another player - most likely by startups.
By this time the large percentage of day-to-day transactions have shifted to mobile banking; here are some overriding areas QAs must investigate while testing mobile banking apps.  
Introduction to Processes
Starting up a Project

580 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question