Software Project Scope Quiz: How to Avoid Scope Creep - The Blytheco Blog
Software Project Scope Quiz: How to Avoid Scope Creep

Software Project Scope Quiz: How to Avoid Scope Creep


According to one recent report, more than 29% of ERP implementations fail to achieve even half the planned business benefits—and that is mostly due to failure in planning.

Do you know how to avoid this common—but painful—mistake?

Defining and then managing the scope of your software project is the key, but do you know what you need to about this key step? Take our short quiz now and find out.

Software Project Scope Quiz

  • Scope affects what two other key factors in a project?
  • Time and cost
  • Cost and promotions
  • Time and type of software
  • What is one way to manage project scope when the list of desired requirements is beyond what can be accomplished in the planned project?
  • Ignore some of the requirements
  • Buy additional software for those other requirements
  • Stage the project so that additional requirements can be addressed after the initial requirements are completed
  • Key steps in defining software project scope include all except:
  • Define the Scope Owner and team
  • Collect requirements
  • Include every requirement requested by team members
  • Define a change control process
  • Define the desired tasks
  • Validate those tasks with stakeholders and Executive sponsor
  • When collecting and prioritizing the system requirements, it’s most important to gather information from:
  • A large group of users to get a broad perspective
  • A small group that is representative of the broader group
  • A small group of recognized experts
  • Software consultants
  • When gathering requirements, is it best to ask:
  • “What functionality do you want?”
  • “What problem are you trying to solve?”
  • “What software do you think we should buy?”

Answers

1. Scope affects what two other key factors in a project?

A. Time and cost

2. What is one way to manage project scope when the list of desired requirements is beyond what can be accomplished in the planned project?

C. Stage the project so that additional requirements can be addressed after the initial requirements are completed

3. Key steps in defining software project scope include all except:

C. Include every requirement requested by team members

4. When collecting and prioritizing the system requirements, it’s most important to gather information from:

A. A large group of users to get a broad perspective

5. When gathering requirements, is it best to ask:

B. “What problem are you trying to solve?”

Whether you scored well on this quiz or not, be sure to join us for our upcoming webinar: How to Define Your Software Project Scope to learn more about defining the scope of software projects. You’ll learn much more about how to prepare your software project for success.

Avatar for Kathy McCoy

Share This Post