- Plan the first product release (
v1.3) - Manage the iteration, and deliver
v1.3Thu, Oct 17th 23:59
Intro to tP Week 9
What's happening this week:
This week, we deliver the first working version of the product (i.e., the MVP), thus finishing what we started in the previous iteration.
v1.3 (MVP)
- Learning outcome: Able to deliver a fully working product, on time.
- Product goal: Reach the .
- Strategy: Decide on a plan to meet the MVP delivery deadline. Reduce risk by aiming for the smallest subset of must-have features.
As per the learning outcome of this iteration (given above), our focus is on delivering a product on time. So, in task 1, we start by setting up a plan to reach that goal, and then execute on it in task 2 , while making course corrections as we go (if needed).
Things to note:
Iteration vs milestone vs version:
An iteration can aim to reach zero or more milestones, some of which can be the release of a product version. So, they are three different things.
For convenience, the tP uses a version number to refer to all three. For example, when we say iteration v1.3, we mean the iteration that ends in the milestone v1.3 (that also happens to deliver the product version v1.3).
How to define version numbers?
While there is no universal set of rules on choosing version numbers for a product, there is a convention named SemVer that is well-defined and widely used. Our tP version numbers (v1.3, v1.5, v1.6 etc.) do not follow SemVer strictly though.
1 Plan the first product release (v1.3)
Note that the product you deliver at the end of this iteration must be working although the functionality is basic.
-- [More details to be added] --
- Revise MVP design, if necessary.
- Enumerate the tasks to be done, order, timeline
- create as issues -> assign member, milestone
2 Manage the iteration, and deliver v1.3 Thu, Oct 17th 23:59
- Manage the iteration
v1.3, and reach the milestonev1.3(which delivers product versionv1.3) as explained in the panel below.
Ways to level up your tP game:
- Consider updating the UG as you go. As you implement a feature/enhancement, consider updating the user guide (UG) to match the new behavior.
- Start reviewing each other's PRs seriously, and giving thoughtful review comments (i.e., as opposed to approving after a superficial look), if you haven't done so already.
- Aim to delivery on time, as that is linked to our tP learning outcome of this iteration. This means you need to monitor progress, and course-correct as you go.
- Revise the MVP design further, if needed. If you think some of the ongoing work intended for the current iteration may not finish in time, you can reassign them to a future iteration, provided they are not essential for the
v1.3(i.e., you can still get a 'working product' without them). - or issues/PR accordingly.
- Revise the MVP design further, if needed. If you think some of the ongoing work intended for the current iteration may not finish in time, you can reassign them to a future iteration, provided they are not essential for the
- Do a release on GitHub, when the product
v1.3is ready. Requirements:- Write a fairly detailed Release Note in the text field GitHub provides for the description of the release. In particular, describe what has been changed (compared to AB3). This is just an itemized list of What's New -- no need to be as elaborate as a user guide.
Include screenshots (or screen recordings) of your product in action, featuring the changes you've done.
These release notes will be checked by the teaching team to verify (a) that they are written reasonably well, and, (b) that the features mentioned in there show the product has reached the MVP level of functionality. - Upload the JAR file as well. Instructions for creating a JAR file can be found in as described in the tP Developer Guide.
- Write a fairly detailed Release Note in the text field GitHub provides for the description of the release. In particular, describe what has been changed (compared to AB3). This is just an itemized list of What's New -- no need to be as elaborate as a user guide.
- Wrap up the milestone on GitHub, when you are done with this iteration and the MVP has been released.