Once the system requirements are identified and prioritized, shouldnt everything be frozen to prevent scope or feature
Question:
Once the system requirements are identified and prioritized, shouldn’t everything be frozen to prevent scope or feature creep? Doesn’t updating the project plan or allowing stakeholders to continue to request changes just delay system design and construction, and maybe even project completion itself?
Fantastic news! We've Found the answer you've been seeking!
Step by Step Answer:
Answer No freezing everything after identifying and prioritizing system requirements is not always the best approach While it is essential to have a c...View the full answer
Answered By
Cyrus Sandoval
I a web and systems developer with a vast array of knowledge in many different front end and back end languages, responsive frameworks, databases, and best code practices. My objective is simply to be the best web developer that i can be and to contribute to the technology industry all that i know and i can do. My skills include:
- Front end languages: css, HTML, Javascript, XML
- Frameworks: Angular, Jquery, Bootstrap, Jasmine, Mocha
- Back End Languages: Java, Javascript, PHP,kotlin
- Databases: MySQL, PostegreSQL, Mongo, Cassandra
- Tools: Atom, Aptana, Eclipse, Android Studio, Notepad++, Netbeans.
Having a degree in Computer Science enabled me to deeply learn most of the things regarding programming, and i believe that my understanding of problem solving and complex algorithms are also skills that have and will continue to contribute to my overall success as a developer.
I’ve worked on countless freelance projects and have been involved with a handful of notable startups. Also while freelancing I was involved in doing other IT tasks requiring the use of computers from working with data, content creation and transcription.
1+ Reviews
10+ Question Solved
Related Book For 
Introduction To Systems Analysis And Design
ISBN: 9780073402949
1st Edition
Authors: Jeffrey Whitten, Lonnie Bentley
Question Posted:
