Introduction to Software Product Management complete course is currently being offered by University of Alberta through Coursera platform. 

This course is part of the Software Product Management Specialization.

About this Course

This course highlights the importance and role of software product management. It also provides an overview of the specialization, as well as its goals, structure, and expectations. 

The course explains the value of process, requirements, planning, and monitoring in producing better software.


- Relate software product management to better software products
- Recognize the role of a software product manager
- Reflect on how Agile principles will improve your own projects


- Agile Software Development
- Software Product Management
- Software Project Management

Introduction to Software Product Management Quiz Answers - Coursera!

Module 1 - Graded Quiz Answers

Q1. What are examples of desirable characteristics that effective software product management can help to achieve?

  • the client specifies requirements; demo is delivered at the end; satisfied developers
  • a satisfied client; the project is on time; lots of overtime hours for developers
  • a satisfied client; having regular client demos; client writes automated tests
  • having regular client demos; meeting client needs; having clear project progress

Q2. As a software product manager, you could be interacting with many business units, such as the executive, marketing, and support. Day to day, however, you mostly focus on representing the needs of two parties, _____ and _____.

  • development team
  • end-user
  • client
  • CEO

Q3. When we have the software product done right, we say the software product is ____.

  • validated
  • certified
  • verified

Q4. In the four foundational courses, what are the next two courses after the introduction that are the basis for the “planning” course and signified by the legs of an inukshuk?

  • Agile Planning for Software Products
  • Reviews and Metrics for Client Needs
  • Client Needs and Software Requirements
  • Software Processes and Agile Practices

Module 2 - Graded Quiz Answers

Q1. According to a survey conducted in 2013 by Scott Ambler + Associates, 58% of respondents defined project success by what criteria?

  • project on schedule
  • project on budget
  • project meets specification
  • all of the above

Q2. The Manifesto for Agile Software Development specifically says it values ____ over comprehensive documentation?

  • customer collaboration
  • responding to change
  • working software
  • individuals and interactions

Q3. The Manifesto for Agile Software Development says it values ____ less.

  • following a plan
  • individuals and interactions
  • working software
  • customer collaboration

Q4. As an Agile principle, what is the primary measure of progress in the project?

  • working software
  • technical excellence
  • sustainable development
  • satisfying the customer

Q5. In a software process, in which phase do you determine what the software is expected to do?

  • design and implementation
  • specification
  • verification and validation
  • planning

Q6. What potential benefits does following a process for software development have?

  • features are defined; ad hoc development is followed; defects are found
  • work expectations are set; poor designs are detected; resources are wasted
  • responsibilities are defined; project are monitored; risks are managed
  • quality is improved; roles are defined; coding is from imagination

Q7. Spending time on refining software requirements primarily helps to ______.

  • detect potential misunderstandings in your product before it is built
  • polish the expression of the requirements, so no further edits are needed
  • show the implementation details of how the product works internally
  • ensure the software requirements are all known in the beginning

Q8. According to Alan Lakein, planning is about ___ so that you can do something about it now.

  • bringing the past into the present
  • bringing experience into the present
  • bringing the past into the future
  • bringing the future into the present

Final Assessment Answers

Q1. From the course, what are the viewpoints to achieving better software?

  • The right product, the right process, and the right people.
  • The right product, done right, and managed right.
  • The right product, the right client, and the right developers.
  • The right product, the right timing, and the right funding.

Q2. To achieve better software, one viewpoint aims to have the right product. What does having the right product mean?

  • The developers are satisfied with the product.
  • The client is satisfied that the product meets their needs.
  • The product conforms to the specified requirements.
  • The product functionality does not have defects.

Q3. When we have the right software product, we say the software product is ____.

  • validated
  • certified
  • verified

Q4. To achieve better software, another viewpoint aims to have the product done right. What ways can developers achieve that? Choose two of the following:

  • Developers request a list of requirements from the client.
  • Developers review the requirements so that they are clear and consistent.
  • Developers show the product to the client to see if it meets their needs.
  • Developers run tests to check whether the product conforms to the specified requirements.

Q5. What is the primary agile principle that can lead to better software products and project success?

  • Information is conveyed effectively in the development team through instant messaging.
  • Working software is delivered every six months to allow time for more changes.
  • The best designs emerge from teams that follow a visionary leader.
  • The customer is satisfied with the early and continuous delivery of valuable software.

Q6. The Manifesto for Agile Software Development puts more value on:

  • responding to change, individuals and interactions, and working software.
  • individuals and interactions, working software, and following a plan.
  • working software, customer collaboration, and processes and tools.
  • customer collaboration, responding to change, and comprehensive documentation.

Q7. When the Manifesto for Agile Software Development says it values responding to change over following a plan, it means

  • responding to change is valued more than following a plan.
  • plan for change for more value.
  • plans can change, so they have less value.
  • changing plans are valued more.

Q8. As an Agile principle, what is harnessed for the customer’s competitive advantage?

  • change
  • valuable software
  • simplicity
  • motivated individuals

Q9. What does a software process organize?

  • It organizes how software products help people to do work in phases.
  • It organizes how the work of people is assisted with software to develop products.
  • It organizes how the work of people happens in distinct phases to develop a software product.
  • It organizes how software operates on information in distinct phases.

Q10. In this specialization, what are software requirements?

  • They are specific descriptions of your client’s needs.
  • They are specific descriptions of what your client wants.
  • They are specific descriptions of what your client needs in order to run the software. 
  • They are specific hardware that the software needs to run. 

Q11. Clear expressions of software requirements are important to help _____.

  • the client express themselves clearly
  • avoid confusion between the client and developers
  • ensure the software requirements are legible by those with poor eyesight
  • produce transparent effects in the user interface of a software product

Q12. Planning initially involves using information from ___ for developers to devise needed tasks and make time estimates.

  • requirements
  • delivery targets
  • schedules
  • calendars

Q13. What are direct benefits or outcomes of using planning?

  • risks are identified; risks are monitored; overcommitment can be avoided 
  • requirements are defined; task times are estimated; tasks are assigned 
  • risks are managed; plans are fixed; tasks are assigned
  • tasks are determined; tasks are assigned; schedules are created

Q14. You need to effectively monitor, analyze, and review the progress of your project, so you:

  • can boost morale before crunch time comes. 
  • monitor velocity to help in continuously adjusting plans.
  • track ongoing work to ensure management knows the status.
  • use your gut feelings to assess the project status.

Post a Comment

Previous Post Next Post