├── CITATION.cff ├── CODE_OF_CONDUCT.md └── README.md /CITATION.cff: -------------------------------------------------------------------------------- 1 | cff-version: 1.2.0 2 | title: Milestones Ideas & Examples 3 | message: >- 4 | If you use this work and you want to cite it, 5 | then you can use the metadata from this file. 6 | type: software 7 | authors: 8 | - given-names: Joel Parker 9 | family-names: Henderson 10 | email: joel@joelparkerhenderson.com 11 | affiliation: joelparkerhenderson.com 12 | orcid: 'https://orcid.org/0009-0000-4681-282X' 13 | identifiers: 14 | - type: url 15 | value: 'https://github.com/joelparkerhenderson/milestones/' 16 | description: Milestones Ideas & Examples 17 | repository-code: 'https://github.com/joelparkerhenderson/milestones/' 18 | abstract: >- 19 | Milestones Ideas & Examples 20 | license: See license file 21 | -------------------------------------------------------------------------------- /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | 2 | # Contributor Covenant Code of Conduct 3 | 4 | ## Our Pledge 5 | 6 | We as members, contributors, and leaders pledge to make participation in our 7 | community a harassment-free experience for everyone, regardless of age, body 8 | size, visible or invisible disability, ethnicity, sex characteristics, gender 9 | identity and expression, level of experience, education, socio-economic status, 10 | nationality, personal appearance, race, caste, color, religion, or sexual 11 | identity and orientation. 12 | 13 | We pledge to act and interact in ways that contribute to an open, welcoming, 14 | diverse, inclusive, and healthy community. 15 | 16 | ## Our Standards 17 | 18 | Examples of behavior that contributes to a positive environment for our 19 | community include: 20 | 21 | * Demonstrating empathy and kindness toward other people 22 | * Being respectful of differing opinions, viewpoints, and experiences 23 | * Giving and gracefully accepting constructive feedback 24 | * Accepting responsibility and apologizing to those affected by our mistakes, 25 | and learning from the experience 26 | * Focusing on what is best not just for us as individuals, but for the overall 27 | community 28 | 29 | Examples of unacceptable behavior include: 30 | 31 | * The use of sexualized language or imagery, and sexual attention or advances of 32 | any kind 33 | * Trolling, insulting or derogatory comments, and personal or political attacks 34 | * Public or private harassment 35 | * Publishing others' private information, such as a physical or email address, 36 | without their explicit permission 37 | * Other conduct which could reasonably be considered inappropriate in a 38 | professional setting 39 | 40 | ## Enforcement Responsibilities 41 | 42 | Community leaders are responsible for clarifying and enforcing our standards of 43 | acceptable behavior and will take appropriate and fair corrective action in 44 | response to any behavior that they deem inappropriate, threatening, offensive, 45 | or harmful. 46 | 47 | Community leaders have the right and responsibility to remove, edit, or reject 48 | comments, commits, code, wiki edits, issues, and other contributions that are 49 | not aligned to this Code of Conduct, and will communicate reasons for moderation 50 | decisions when appropriate. 51 | 52 | ## Scope 53 | 54 | This Code of Conduct applies within all community spaces, and also applies when 55 | an individual is officially representing the community in public spaces. 56 | Examples of representing our community include using an official e-mail address, 57 | posting via an official social media account, or acting as an appointed 58 | representative at an online or offline event. 59 | 60 | ## Enforcement 61 | 62 | Instances of abusive, harassing, or otherwise unacceptable behavior may be 63 | reported to the community leaders responsible for enforcement at 64 | [INSERT CONTACT METHOD]. 65 | All complaints will be reviewed and investigated promptly and fairly. 66 | 67 | All community leaders are obligated to respect the privacy and security of the 68 | reporter of any incident. 69 | 70 | ## Enforcement Guidelines 71 | 72 | Community leaders will follow these Community Impact Guidelines in determining 73 | the consequences for any action they deem in violation of this Code of Conduct: 74 | 75 | ### 1. Correction 76 | 77 | **Community Impact**: Use of inappropriate language or other behavior deemed 78 | unprofessional or unwelcome in the community. 79 | 80 | **Consequence**: A private, written warning from community leaders, providing 81 | clarity around the nature of the violation and an explanation of why the 82 | behavior was inappropriate. A public apology may be requested. 83 | 84 | ### 2. Warning 85 | 86 | **Community Impact**: A violation through a single incident or series of 87 | actions. 88 | 89 | **Consequence**: A warning with consequences for continued behavior. No 90 | interaction with the people involved, including unsolicited interaction with 91 | those enforcing the Code of Conduct, for a specified period of time. This 92 | includes avoiding interactions in community spaces as well as external channels 93 | like social media. Violating these terms may lead to a temporary or permanent 94 | ban. 95 | 96 | ### 3. Temporary Ban 97 | 98 | **Community Impact**: A serious violation of community standards, including 99 | sustained inappropriate behavior. 100 | 101 | **Consequence**: A temporary ban from any sort of interaction or public 102 | communication with the community for a specified period of time. No public or 103 | private interaction with the people involved, including unsolicited interaction 104 | with those enforcing the Code of Conduct, is allowed during this period. 105 | Violating these terms may lead to a permanent ban. 106 | 107 | ### 4. Permanent Ban 108 | 109 | **Community Impact**: Demonstrating a pattern of violation of community 110 | standards, including sustained inappropriate behavior, harassment of an 111 | individual, or aggression toward or disparagement of classes of individuals. 112 | 113 | **Consequence**: A permanent ban from any sort of public interaction within the 114 | community. 115 | 116 | ## Attribution 117 | 118 | This Code of Conduct is adapted from the [Contributor Covenant][homepage], 119 | version 2.1, available at 120 | [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1]. 121 | 122 | Community Impact Guidelines were inspired by 123 | [Mozilla's code of conduct enforcement ladder][Mozilla CoC]. 124 | 125 | For answers to common questions about this code of conduct, see the FAQ at 126 | [https://www.contributor-covenant.org/faq][FAQ]. Translations are available at 127 | [https://www.contributor-covenant.org/translations][translations]. 128 | 129 | [homepage]: https://www.contributor-covenant.org 130 | [v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html 131 | [Mozilla CoC]: https://github.com/mozilla/diversity 132 | [FAQ]: https://www.contributor-covenant.org/faq 133 | [translations]: https://www.contributor-covenant.org/translations 134 | 135 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Milestones Ideas & Examples 2 | 3 | Project management milestones ideas and examples. Credit to [BrightHub](http://www.brighthubpm.com/project-planning/68429-project-planning-typical-milestones/). 4 | 5 | Contents: 6 | 7 | * [Introduction](#introduction) 8 | * [How to Classify Typical Milestones](#how-to-classify-typical-milestones) 9 | * [Phase transitions](#phase-transitions) 10 | * [Rates of Completion](#rates-of-completion) 11 | * [Performance recognition](#performance-recognition) 12 | * [Completion of a deliverable](#completion-of-a-deliverable) 13 | * [Achievement of an outcome](#achievement-of-an-outcome) 14 | * [Major Milestones for Software Projects](#major-milestones-for-software-projects) 15 | * [Concept approval](#concept-approval) 16 | * [Requirements review](#requirements-review) 17 | * [Preliminary design review](#preliminary-design-review) 18 | * [Critical design review](#critical-design-review) 19 | * [Test plan review](#test-plan-review) 20 | * [Test readiness review](#test-readiness-review) 21 | * [System test review](#system-test-review) 22 | * [Operational readiness review](#operational-readiness-review) 23 | * [Product operational](#product-operational) 24 | * [Minor Milestones for a Software Project](#minor-milestones-for-a-software-project) 25 | * [Document outline complete](#document-outline-complete) 26 | * [Document complete](#document-complete) 27 | * [Technical investigation complete](#technical-investigation-complete) 28 | * [Compile complete](#compile-complete) 29 | * [Software module complete](#software-module-complete) 30 | * [Software product build complete](#software-product-build-complete) 31 | * [Test case complete](#test-case-complete) 32 | * [Bug fix complete](#bug-fix-complete) 33 | 34 | 35 | ## Introduction 36 | 37 | 38 | ### How to Classify Typical Milestones 39 | 40 | Typical milestones in project planning are often tied to a quantitative measurement, an internal or external deliverable, or a significant turning point or transition in the project. 41 | 42 | To determine which milestones are right for your project select ones that will give you regular feedback about the progress of your project, give team members a boost in morale, and align with the critical path of your project. Milestones can be grouped under several classifications that serve these distinct purposes. 43 | 44 | 45 | ### Phase transitions 46 | 47 | Phase transitions are probably the best known milestones. They are typically used for projects that concentrate on developing or expanding a product or service. The exact process will vary from designer to designer, but the method can divided into six basic stages: information gathering, or marketing research, planning, design, development, testing, and delivery. 48 | 49 | 50 | ### Rates of Completion 51 | 52 | Rates of Completion are commonly used milestones when the project involves repetition without sequential advancement to the next stage. A good example is a training exercise in which milestones are set for the percentage of employees fully trained or certified, e.g., 25, 50, 75, and 100 percent. The incremental benefits of having a certain level of employees certified is a good choice for a milestone. 53 | 54 | 55 | ### Performance recognition 56 | 57 | Performance recognition milestones are achievements that are not directly connected to the advancement of the project, but recognize the quality of the work performed. For example, in the construction of a plant, a typical milestone would be to recognize periodically that employees have logged in a certain number of work hours without a single safety incident. 58 | 59 | 60 | ### Completion of a deliverable 61 | 62 | Completion of a deliverable is by far the most popular choice for a milestone because it represents tangible evidence of progress towards the project's goals. 63 | 64 | 65 | ### Achievement of an outcome 66 | 67 | Achievement of an outcome can be useful for value based consulting, joint partnerships, and profit sharing projects. An represents measurable evidence of success towards the project's goals. 68 | 69 | 70 | ## Major Milestones for Software Projects 71 | 72 | Major milestones give visibly or progress to people external to the project. For example, project sponsors and customers. The list below provides a set of classical major software project milestones together with their milestone goals. 73 | 74 | 75 | ### Concept approval 76 | 77 | Feasibility studies and basic system concepts have been approved by management and the project is authorized to proceed to detailed requirements definition. 78 | 79 | 80 | ### Requirements review 81 | 82 | Requirements specifications are complete, correct, approved and suitable for input to design. 83 | 84 | 85 | ### Preliminary design review 86 | 87 | The architectural design satisfies all product requirements, is approved and is suitable for input into the detailed design process. 88 | 89 | 90 | ### Critical design review 91 | 92 | Detailed designs fully implement the system architecture, are approved and are suitable for input into the development of code. 93 | 94 | 95 | ### Test plan review 96 | 97 | Test plans are adequate for the testing of all product features, are approved and are suitable for input to the development of test cases and test procedures. 98 | 99 | 100 | ### Test readiness review 101 | 102 | Developed and unit tested software has been passed by the test team and is suitable for input into integration testing. 103 | 104 | 105 | ### System test review 106 | 107 | The software product has passed system testing and is suitable for input into acceptance testing. 108 | 109 | 110 | ### Operational readiness review 111 | 112 | The software product has passed acceptance testing and is suitable for deployment in its target production environment. 113 | 114 | 115 | ### Product operational 116 | 117 | The software is in use in its target operational environment. 118 | 119 | 120 | ## Minor Milestones for a Software Project 121 | 122 | Minor milestones are the monitoring points you as project manager use to maintain control of day to day activities. They divide the elapsed time between major milestones into shorter intervals to give you the confidence that the major milestones will be met. They also give the team a sense of achievement by demonstrating progress on a daily or weekly basis. The list below provides examples. 123 | 124 | 125 | ### Document outline complete 126 | 127 | A document outline has been produced describing the format, content and objectives of each major section of a large document. 128 | 129 | 130 | ### Document complete 131 | 132 | A document such as an Software Requirements Specification has passed peer review. 133 | 134 | 135 | ### Technical investigation complete 136 | 137 | The investigation of a technical issue is complete and a summary of the main issues and conclusions has been presented and approved. 138 | 139 | 140 | ### Compile complete 141 | 142 | A program compiles without errors. 143 | 144 | 145 | ### Software module complete 146 | 147 | A small program or function has been completed and unit tested. 148 | 149 | 150 | ### Software product build complete 151 | 152 | The software product (or one of its components) has been built an it runs (not necessarily without errors). 153 | 154 | 155 | ### Test case complete 156 | 157 | A small unit of testing has been completed and test results recorded. 158 | 159 | 160 | ### Bug fix complete 161 | 162 | A bug identified in a Software Anomaly Report (SAR) has been fixed and the SAR closed out. 163 | --------------------------------------------------------------------------------