How can I stay on track if they won't let us do requirements work?
I've been told that since this IT project won't actually change any functionality, we should go do this without customer or business involvement, and they'll just test it at acceptance. How can I manage our project successfully when they won't let us do requirements?
When the conversation with Management is "we don't need to do requirements," we have to start by looking at how Management seems to be thinking of requirements:
"We don't need to do requirements work because the functionality isn't changing."
"Requirements gathering just gives them an opening to change something." Sometimes this will manifest as time pressure instead: "Requirements gathering always takes a big chunk of the schedule, and we need this done FAST."
One plan of attack, no matter what type of project you're leading, is to get them to move away from this negative viewpoint to a more positive connotation of "requirements work."
Log in or Subscribe now to read the full answer...
This resource requires a Premium Subscription
Please log in. Don't have a log-in? Sign up now. Already a Member? Log in to upgrade immediately and get the full answer! A Premium subscription is only $14.95/month or $149/year and gets you over 200 templates, guidelines, and checklists.
15-day free trial period for new Premium subscribers! Learn more
Special: This Premium resource is free to registered Members until January 5, 2012!