Suborbital-Systems-Public/ReadySetGit
3
0
Fork 0
Code Pull Requests Packages Projects Releases Activity

changes for GFM format

Browse Source
This commit is contained in:
William Sandner
2018-08-14 17:15:49 +02:00
parent 757571a6b5
commit f9f546221a
20 changed files with 42 additions and 420 deletions
Download Patch File Download Diff File Expand all files Collapse all files

39
Project-Plan.md
View File

@@ -1,17 +1,17 @@
##### Project:
[::PROJECTNAME](Home.md)
::[PROJECTNAME](Home)
##### Project Time-frame:
::STARTDATE - ENDDATE
##### Attached worksheets:
- Plan > [Resource needs](resource-needs.html)
- Plan > [Resource Needs](Resource-Needs)
##### Related Documents:
- [Project proposal](proposal.html) > [Target audience and benefits](target-and-benefits.html)
- [Software development methodology](sdm.html)
- [Glossary](glossary.html)
- [Project Proposal](Proposal) > [Target audience and benefits](Target-and-Benefits)
- [Software development methodology](SDM)
- [Glossary](Glossary)
---
@@ -24,7 +24,6 @@ project.
needed. Use the worksheet to help identify and scope resource needs.*
### Summary of Project
#### What are the business problem, scope, and goal of this project?
For a summary of this project, see the [Project proposal](proposal.html).
@@ -32,7 +31,7 @@ For a summary of this project, see the [Project proposal](proposal.html).
#### Who will sponsor, manage, and lead the project?
- ::Sponsor: PERSON-NAME
- ::Manager: PERSON-NAMEhtml
- ::Manager: PERSON-NAME
- ::Technical lead: PERSON-NAME
#### What authority does the project manager have?
@@ -43,7 +42,7 @@ For a summary of this project, see the [Project proposal](proposal.html).
- ::Assign specific tasks to other departments
- ::Negotiate requirements and schedules with customers
- ::Negotiate with vendors, suppliers, and partners
html
#### What planning lessons were learned in previous releases?
::None yet. This is the first release.
@@ -54,7 +53,7 @@ html
- ::There are always defects. We planned time to test, but we forgot to plan time to fix the defects.
On this project, we will actually estimate the number of undetected defects.
- ::Issue XXXX made us realize that we forgot to plan time for DEVELOPMENT-TASK.
html
### Summary of Methodology
 
#### What general development approach will be used?
@@ -70,7 +69,7 @@ For more information see the [Software Development Methodology](sdm.html).
#### What development and collaboration tools will be use?
::We plan to use the following tools extensively through out the project:html
::We plan to use the following tools extensively through out the project:
- ::Project website
- ::Project mailing lists
@@ -90,7 +89,7 @@ For more information see the [Software Development Methodology](sdm.html).
complete](glossary.html#featurecomplete) milestone, no
new features will be added to this release.
- ::After the [code complete](glossary.html#codecomplete)
milestone, no entirely new product source code will be added to">Readyset GFM</a>
milestone, no entirely new product source code will be added to
this release.
- ::All source code commit log messages must refer to a specific
issue ID, after the feature complete milestone.
@@ -123,7 +122,7 @@ finished. Don't worry about renumbering if you delete a step.*
| 2. | ::Inception | |
| 2.1. | ::Requirements gathering | 30h |
| 2.2. | ::Requirements specification | 20h |
| 2.3. | ::Requirements validation | 10h |">Readyset GFM</a>
| 2.3. | ::Requirements validation | 10h |
| 3. | ::Elaboration | |
| 3.1. | ::High-level design | 5h |
| 3.2. | ::Low-level design (break down by component) | |
@@ -154,7 +153,7 @@ finished. Don't worry about renumbering if you delete a step.*
### Deliverables in this Release
*TODO: List project deliverables in detail, with delivery dates.*">Readyset GFM</a>
*TODO: List project deliverables in detail, with delivery dates.*
| Deliverable Name | Description | Delivery Date |
|------------------|---------------------------------------------------------------|---------------|
@@ -164,7 +163,7 @@ finished. Don't worry about renumbering if you delete a step.*
| Deliverable Name | ::Description | Delivery Date |
### Schedule for this Release
html
*TODO: Make the rows in this table match the steps in your WBS above. If
you have a large number of detailed steps, you can skip the most
detailed ones. The columns of the table represent weeks of calendar
@@ -218,7 +217,7 @@ Please see the [risks worksheet](risks.html).
design and implementation.
3. ::The schedule for this project is very short. We will manage this by
planning a conservatively scoped functional core and series of
functional enhancements that can be individually slipped to later">Readyset GFM</a>
functional enhancements that can be individually slipped to later
releases if needed.
4. ::The performance of the system will be significantly impacted by the
decisions made during the [database design task](#3.2.C). None of
@@ -266,10 +265,10 @@ Please see the [risks worksheet](risks.html).
::No, this project stands alone.
::Yes, project P1 must provide library L, and project P2 must prove">Readyset GFM</a>
::Yes, project P1 must provide library L, and project P2 must prove
the usability of feature F, and....
#### Does any other project depend on this project?html
#### Does any other project depend on this project?
::No, project is not producing any components that will be used in
other current projects.
@@ -279,10 +278,6 @@ L in projects P1 and P2.
#### Are there any other important dependencies that will affect this project?
::No, everything is covered above.html
::No, everything is covered above.
::Yes. DETAILS....
<!-- words of wisdom -->
---
***TODO:*** *Check for [words of widsom](http://readyset.tigris.org/words-of-wisdom/overview.html) and discuss ways to improve this template. Or, evaluate the ReadySET Pro [professional project plan template](http://www.readysetpro.com/) professional project plan template.*