Solved

How rigid is your design specification?

Posted on 2014-10-05
2
218 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 500 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

Is Your Active Directory as Secure as You Think?

More than 75% of all records are compromised because of the loss or theft of a privileged credential. Experts have been exploring Active Directory infrastructure to identify key threats and establish best practices for keeping data safe. Attend this month’s webinar to learn more.

Question has a verified solution.

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

Communication between departments might not happen in two different languages, but they do exist in two different worlds. With different targets and performance goals the same phrase often means something completely different to each party. Learn ho…
The Quality Assurance engineer of an Agile scrum team must "own" the acceptance criteria for sprint tasks.
Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.
This video demonstrates how to create an example email signature rule for a department in a company using CodeTwo Exchange Rules. The signature will be inserted beneath users' latest emails in conversations and will be displayed in users' Sent Items…

914 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

Need Help in Real-Time?

Connect with top rated Experts

22 Experts available now in Live!

Get 1:1 Help Now