tP: v1.3
v1.3
)v1.3
Thu, Oct 17th 23:59What'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)
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.
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] --
v1.3
Thu, Oct 17th 23:59v1.3
, and reach the milestone v1.3
(which delivers product version v1.3
) as explained in the panel below.Ways to level up your tP game:
v1.3
(i.e., you can still get a 'working product' without them).v1.3
is ready. Requirements: