Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
In this six-week capstone course, you will gain practical management experience in a safe, simulated software production setting. You will apply Agile practices and techniques to conquer industry-inspired challenges. Interacting with a realistic client, you will discern what they want and express what they truly need in software requirements to drive software production. Upon completing the capstone, you will be prepared to advance your career as a confident software product management professional.
In this assignment, you will create a Requirements document based on the information that you elicited from your interactions with your client and the expert, as well as the information discussed with the development team.
Instructions:
You will not be commenting on your peer’s Requirements document in this assignment. You will be making comments to your peer’s Requirements document in Week 2 during the Requirements Technical Review assignment.
In this assignment, you will submit the URL to your Requirements document again (i.e., you are copying and pasting the URL from the Requirements document that you created for Assignment 1.9). Then the real work for this assignment is in the peer review.
During the peer review, you will receive a link to your peer’s Requirement document. You are to go into the document and make comments and suggestions.
You are going to need to save the URLs of the documents that you perform the review on, so make sure to keep track of them. You also need to take some screenshots of your work to prove that you completed the review. These will be submitted in the next assignment.
To make edits to your peer’s work:
When you are reviewing, you should:
Classify the findings into major, moderate, or minor levels of severity:
All suggestions for your peer should be made on the Google Document, so your peer can see the improvements that you suggested.
In the last assignment, you should have completed a Requirements Technical Review and saved the URLs and screenshots.
In this assignment, you are going to upload those screenshots and URLs, and get graded on your participation and execution.
In this assignment, you will be creating a Risk Plan for the team and the product.
You just talked with the team about risks that they think they may encounter in the project. You are going to use information from this conversation to generate a Risk Plan for the product.
Your Risk Plan should include:
For each risk:
You can choose to 1) write out your Risk Plan in the text box or 2) create a Google document and submit the link as a hyperlink.
*Update on Feb 18, 2021: If you choose to submit via Google doc:
You will be submitting your results from the Release Planning Interactive Learning Object.
Complete that activity if you have not done so already, and make sure that you press the Download PDF button. You may complete this activity as many times as you wish until you achieve the desired results.
Following this assignment, we will be synchronizing the class by providing everyone with a Release Plan to work with. You will receive the Release Plan, as well as an explanation for why we chose the user stories. This document will remain locked until you pass this assignment, so you will not be able to view the Release Plan until your peers have graded your assignment. It is possible to continue with the rest of the videos and/or assignments in this week, but you may be missing information.
Upload the produced PDF to the Coursera platform.
The development team has broken down the user stories for Sprint 1 into tasks. They have also estimated and self-assigned themselves to tasks. They want to run it by you before the sprint begins.
In this assignment, you will be evaluating the iteration plan provided by the development team. Provide them feedback (both positive and negative) on what you see on the iteration plan.
Go to the My Submission tab to access the iteration plan.
With the first sprint right around the corner, Lisa wanted to see a rough idea for the product. The development team asked you if you could draft up a wireframe that highlights the basic functionalities of the product.
Generate a wireframe for the product. You can demonstrate any “page” of the application (i.e. you could choose to show the page that the user sees when they are reading, the page they see when they are browsing, searching, etc.)
You only need to demonstrate one page of the application and not all functionalities need to be demonstrated. (Feel free to include more than one page in your submission, if you want.)
You need to write acceptance criteria and tests for the following user stories in this sprint:
For each user story, you must include at least two acceptance criteria, and for each criterion, you must include at least one acceptance test. You may include more acceptance criteria or tests if necessary to the user story.
You may submit your acceptance criteria and tests in the text box below or use a Google Document and submit the URL in the text box. Make sure that if you choose to use Google Docs, that your assignment is set to “Comments Only” mode.
Since this is the first week of development, a release burndown does not show a lot of information. For that reason, you are going to practice making an Iteration Burndown for this sprint.
Use the information found on this spreadsheet to create an Iteration Burndown for this sprint.
Include a prediction line in your Iteration Burndown.
Upload your burndown as a JPEG, PNG, or PDF file and answer the questions about the Iteration Burndown.
In this Assignment you will be submitting your results from the Release Planning Interactive Learning Object.
Complete the Release Planning activity and press the Download PDF button. You may complete this activity as many times as you wish until you achieve the desired results.
Following this assignment, we will be synchronizing the class by providing everyone with a release plan to work with. You will receive the Release Plan, as well as an explanation for why we chose the user stories. This document will remain locked until you pass this assignment, so you will not be able to view the release plan until your peers have graded your assignment. It is possible to continue with the rest of the videos and/or assignments in this week, but you may be missing information.
Upload the produced PDF to the Coursera platform.
The development team has broken down the user stories for Sprint 2 into tasks. They have also estimated and self-assigned themselves to tasks. They want to run it by you before the sprint begins.
In this assignment, you will be evaluating the Iteration Plan provided by the development team. Provide them feedback (both positive and negative) on what you see on the Iteration Plan. Your evaluation should include at least three pieces of feedback.
Go to the My Submission tab to access the Iteration Plan.
In this assignment, you will be updating the Risk Plan for the team and the product.
At the previous standup, Josh talked about how many of the features in this sprint are dependant on the database connection feature. This poses a risk to the project.
Create a new entry for your Risk Plan to cover a contingency plan if the database connection feature cannot be developed in this sprint.
You are also going to add one other additional risk to your Risk Plan that might affect development. This risk can be anything related to the project so far. Have you noticed something that has the potential to be an issue?
You only need to add the two new risks. You do not need to write out your previous Risk Plan.
Your Risk Plan should include:
For each risk:
You will be submitting your results from the Release Planning Interactive Learning Object.
Complete the Release Planning activity and press the Download PDF button. You may complete this activity as many times as you wish until you achieve the desired results.
Following this assignment, we will be synchronizing the class by providing everyone with a Release Plan to work with. You will receive the Release Plan, as well as an explanation for why we chose the user stories. This document will remain locked until you pass this assignment, so you will not be able to view the Release Plan until your peers have graded your assignment. It is possible to continue with the rest of the videos and/or assignments in this week, but you may be missing information.
Upload the produced PDF to the Coursera platform.
In this second sprint of development, you are going to be creating a Release Burndown for the work completed thus far.
This week, you are going to create a Release Burndown chart for the work completed so far in the project.
Use the information found on this spreadsheet to create a Release Burndown. You need to demonstrate the change in the number of user stories in your release plan.
Include a prediction line in your Release Burndown. This prediction line should predict the velocity that the team should maintain if they want to complete all the user stories currently in the backlog over five sprints.
Upload your burndown as a JPEG, PNG, or PDF file and answer the questions about the Release Burndown.
Hint: Check out this Release Burndown How-to from the Reviews and Metrics course:
The development team has broken down the user stories for Sprint 3 into tasks. They have also estimated and self-assigned themselves to tasks. They want to run it by you before the sprint begins.
In this assignment, you will be evaluating the Iteration Plan provided by the development team. Provide them feedback (both positive and negative) on what you see on the Iteration Plan. Your evaluation should include at least three pieces of feedback.
Go to the My Submission tab to access the Iteration Plan.
In this third sprint of development, you are going to be creating a Release Burndown for the work completed thus far.
Use the information found on this spreadsheet to create an Release Burndown. You need to demonstrate the change in the number of user stories in your Release Plan. The team has decided to remove the user stories about the Favorites List (US#16 and US#17) from the project because Lisa liked the product having only one list.
Include a prediction line in your Release Burndown. This prediction line should predict the velocity the team should maintain if they want to complete all the user stories currently in the backlog over five sprints.
Upload your burndown as a JPEG, PNG, or PDF file and answer the questions about the Release Burndown.
Hint: Check out this Release Burndown How-to from the Reviews and Metrics course:
In this assignment, you will be reflecting on your own personal experience of this capstone and specialization.
This assignment is graded based on participation and not on your perspective.
Congratulations! You have made it to the end. We want to hear about your experience with this capstone and specialization.
Please take some time and reflect on the things that you have learned, your favorite parts, the overall experience, and things we can improve. Feel free to elaborate on whatever you want.
I hope this Software Product Management Capstone Peer-graded Assignment Solution would be useful for you to learn something new from this Course. If it helped you then don’t forget to bookmark our site for more peer graded solutions.
This course is intended for audiences of all experiences who are interested in learning about new skills in a business context; there are no prerequisite courses.
Keep Learning!
More Peer-graded Assignment Solutions >>
Qualitative Research Methods Peer-graded Assignment Solutions
Machine Learning with Python Peer-graded Assignment Solutions