-
Notifications
You must be signed in to change notification settings - Fork 0
Glossary
A single or a list of quantifiable and achievable milestone(s), which when fulfilled, mark the completion of an effort. The milestones need to be carefully curated such that no ends are left unbounded
Example: Consider a task to make yourself a cup of espresso. The definition of done can be listed as the following milestones
- An aromatic, tasty and hot beverage made from the best espresso beans at hand using the best practices.
- Clean station once beverage has been made
The time when to do this task or effort. Is it something early ? Can it be postponed to a later stage ? Or is it something completely out of the scope of this timeline. For this document, I will use
- Step-1 as something that needs to be done before anything
- Early is something to be taken care of in the very early stages
- Later Something that can be done in parallel or maybe even postponed to a future stage of the project
- Post live Something to be taken care of in very later stages, stuff that can be postponed until e.g after MVP-1 is live or when some users are already using your product.
The size of the project. No matter what you are making, a university year end project or a large scale enterprise search engine, there is a certain size of this project. For the sake of simplicity, this document uses
- P (prototype, MVP-1 or version 0.1)
- S (small university activity, freelancer project, early stage startup)
- M (medium sized business, paying customers) and
- L (large enterprise, big client base, higher stakes)
to differentiate the different complexities based on level 1 t-shirt size.
The term originates in hardware repair and has been applied to software. It's intended to be a quick test to see if the application "catches on fire" when run for the first time.