diff --git a/Design-Architecture.md b/Design-Architecture.md index a971df0..2f7ef2e 100644 --- a/Design-Architecture.md +++ b/Design-Architecture.md @@ -1,29 +1,5 @@ - - - - - - ReadySet Markdown - - - - - - Overview - Project Plan - Workflows - Current - - - - -<!-- Markdown content here --> - -# [Design](design.html)&nbsp;&gt;&nbsp;Architecture ---- - ##### Project: -::PROJECTNAME +::PROJECTNAME(Home) ##### Internal Release Number: ::X.Y.Z @@ -40,7 +16,7 @@ architecture. Some example text is provided.* ### Overview -&nbsp; + #### What are the most important facts that a developer should know about this system architecture? ::PARAGRAPH OR BULLETS @@ -64,7 +40,7 @@ architecture. Some example text is provided.* 3. ::[Capacity matching](glossary-std.html#capacity_matching) ### Components -&nbsp; + #### What are the components of this system? ::The components of this system are clearly defined in this [UML Model @@ -80,7 +56,7 @@ architecture. Some example text is provided.* - ::[C-20: COMPONENTNAME](design-components.html#c-20) ### Deployment -&nbsp; + #### How will the components be deployed to processes and machines? ::The deployment of components to processes and machines is clearly @@ -143,7 +119,7 @@ The application logic running on the application server cannot be split or load-balanced. ### Integration -&nbsp; + #### How will components be integrated? Specifically, how will they communicate? @@ -211,25 +187,4 @@ competition for resources. ::Yes, everyone understands. Feedback is welcome. -::No, this is a risk that is noted in the [Risk -Management](plan#risks) section. - -<!-- End Markdown content --> - - -
-
- - - - - - - - - - - - +::No, this is a risk that is noted in the [Risk Management](Project-Plan#risks) section. diff --git a/Design.md b/Design.md index b937ea4..0f29aba 100644 --- a/Design.md +++ b/Design.md @@ -23,7 +23,7 @@ --- ##### Project: -::[PROJECTNAME](index.html) +::[PROJECTNAME]">Readyset GFM ##### Internal Release Number: ::X.Y.Z diff --git a/Interview-Notes.md b/Interview-Notes.md index 103f10c..fa0d126 100644 --- a/Interview-Notes.md +++ b/Interview-Notes.md @@ -23,7 +23,7 @@ --- ##### Project: -::[PROJECTNAME](index.html) +::[PROJECTNAME]">Readyset GFM ##### Interviewer(s): ::PERSONNAME diff --git a/Legal.md b/Legal.md index 9c61886..4162cb7 100644 --- a/Legal.md +++ b/Legal.md @@ -23,7 +23,7 @@ --- ##### Project: -::[PROJECTNAME](index.html) +::[PROJECTNAME]">Readyset GFM ##### Internal Release Number: ::X.Y.Z diff --git a/Plan.md b/Plan.md deleted file mode 100644 index 7121c0e..0000000 --- a/Plan.md +++ /dev/null @@ -1,328 +0,0 @@ - - - - - - ReadySet Markdown - - - - - - Overview - Project Plan - Workflows - Current - - - - -<!-- Markdown content here --> - -# Project Plan ---- - -##### Project: -::[PROJECTNAME](index.html) - -##### Project Time-frame: -::STARTDATE - ENDDATE - -##### Attached worksheets: -- Plan &gt; [Resource needs](resource-needs.html) - -##### Related Documents: - -- [Project proposal](proposal.html) &gt; [Target audience and benefits](target-and-benefits.html) -- [Software development methodology](sdm.html) -- [Glossary](glossary.html) - ---- - -**Process impact:** This plan will be used to evaluate and manage the -project. Key assumptions that affect the plan should be documented here. -The project plan should be updated throughout the life-time of the -project. - -*TODO: Fill in the information above and below. Add or remove rows as -needed. Use the worksheet to help identify and scope resource needs.* - -### Summary of Project -&nbsp; -#### What are the business problem, scope, and goal of this project? - -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-NAME -- ::Technical lead: PERSON-NAME - -#### What authority does the project manager have? - -- ::Hire, dismiss, or reassign personnel in his/her department -- ::Hire contract employees or manage subcontractors -- ::Purchase equipment, software, and other needed capital -- ::Assign specific tasks to other departments -- ::Negotiate requirements and schedules with customers -- ::Negotiate with vendors, suppliers, and partners - -#### What planning lessons were learned in previous releases? - -::None yet. This is the first release. - -- ::We can reduce training time, but it significantly increases development time. -- ::Maintaining a past release takes more than 20% of our time, due to low quality in that release. -- ::The customer seems to always change the requirements after the second demo. -- ::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. - -### Summary of Methodology -&nbsp; -#### What general development approach will be used? - -::THREE TO FIVE SENTENCES OR BULLETS HERE. COVER GENERAL APPROACH, IMPORTANT ASSUMPTIONS, KEY PRACTICES, AND PROJECT COORDINATION CONTROLS. - -For more information see the [Software Development Methodology](sdm.html). - -#### How will the project team be organized? - -- ::The development team will consist of ... -- ::The change control board will consist of ... - -#### What development and collaboration tools will be use? - -::We plan to use the following tools extensively through out the project: - -- ::Project website -- ::Project mailing lists -- ::Issue tracking system -- ::Version control system -- ::Automated build system -- ::Automated unit test system - -#### How will changes be controlled? - -- ::Requests for requirements changes will be tracked in the issue - tracker -- ::The change control board ([CCB](glossary.html#ccb)) - will review requested changes and authorize work on them as - appropriate -- ::After the [feature - 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 - this release. -- ::All source code commit log messages must refer to a specific - issue ID, after the feature complete milestone. - -#### How will this plan be updated? - -::This project plan will be updated as needed throughout the project. -It will be placed under version control and instructions for -accessing it will be on the [project website](index.html). Any -change to the plan will cause an automatic notification to be sent -to a project mailing list. - -### Work Breakdown Structure and Estimates - -*TODO: List tasks that will be needed for this project. Keep dividing -tasks into subtasks until you feel that you have enough detail to expose -risks and make reasonable estimates in ideal engineering hours.* - -*TIP: Label each step uniquely to show its position in the WBS, e.g., -Step 1.1.4.A. Use numbers for steps that you intend to do in sequence, -and use letters for steps that you intend to do in parallel. E.g., Step -1.1 comes before Steps 1.2.A and 1.2.B, but those two steps may be done -in parallel, and Step 1.3 will be done after all 1.2.\* steps have been -finished. Don't worry about renumbering if you delete a step.* - -| Step | Description | Estimate | -|-----------|-----------------------------------------------------------|----------| -| 1. | ::Preparation | | -| 1.1. | ::Developer training | 30h | -| 2. | ::Inception | | -| 2.1. | ::Requirements gathering | 30h | -| 2.2. | ::Requirements specification | 20h | -| 2.3. | ::Requirements validation | 10h | -| 3. | ::Elaboration | | -| 3.1. | ::High-level design | 5h | -| 3.2. | ::Low-level design (break down by component) | | -| 3.2.A. | ::Object design | 10h | -| 3.2.B. | ::User interface design | 10h | -| 3.2.C. | ::Database design | 3h | -| 3.3. | ::Design review and evaluation | 5h | -| 4. | ::Construction | | -| 4.1.A. | ::System implementation | | -| 4.1.A.1. | ::Implement COMPONENT-NAME 1 | 25h | -| 4.1.A.2. | ::Implement COMPONENT-NAME 2 | 25h | -| 4.1.A.3. | ::Implement COMPONENT-NAME 3 | 25h | -| 4.1.A.4. | ::Implement COMPONENT-NAME 4 | 25h | -| 4.1.A.5. | ::Integrate Components (mostly done during implementation)| 5h | -| 4.1.B. | ::Technical documentation (break down by component) | 10h | -| 4.1.C. | ::User documentation (break down by component) | 10h | -| 4.1.D. | ::Testing | | -| 4.1.D.1. | ::Test planning | 10h | -| 4.1.D.2. | ::Test code implementation (break down by component) | 30h | -| 4.1.D.3. | ::Test execution | 10h | -| 4.2. | ::Implementation review and evaluation | 15h | -| 5. | ::Transition | | -| 5.A. | ::Release packaging | 3h | -| 5.B. | ::Documentation for other groups | 3h | -| 6. | ::Reflection | | -| 6.1. | ::Postmortem report | 10h | -| | ::Total | 329 hours| - -### Deliverables in this Release - -*TODO: List project deliverables in detail, with delivery dates.* - -| Deliverable Name | Description | Delivery Date | -|------------------|---------------------------------------------------------------|---------------| -| Deliverable Name | ::Description | Delivery Date | -| Deliverable Name | ::Description | Delivery Date | -| Deliverable Name | ::Description Description Description Description Description | Delivery Date | -| Deliverable Name | ::Description | Delivery Date | - -### Schedule for this Release - -*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 -time. For each cell in the table, enter the number of hours ideal -engineering time that the team will spend on that task that week. Total -your hours across and down.* - -*TIP: These hours should total to the same as the total of the hours -listed in your [resource needs](resource-needs) document. And, the -hours for each type of effort resources needed should correspond to the -sum for each type of task.* - -| Task \ Week | W-01 | W-02 | W-03 | W-04 | W-05 | W-06 | W-07 | W-08 | W-09 | W-10 | W-11 | W-12 | Task Total | -|-----------------|------|------|------|------|------|------|------|------|------|------|------|------|------------| -| ::1. | 00 | 00 | 00 | 00 | 00 | 00 | 00 | 00 | 00 | 00 | 00 | 00 | 00 | -| ::2. | 00 | 00 | 00 | 00 | 00 | 00 | 00 | 00 | 00 | 00 | 00 | 00 | 00 | -| ::3. | 00 | 00 | 00 | 00 | 00 | 00 | 00 | 00 | 00 | 00 | 00 | 00 | 00 | -| ::4.1.A. | 00 | 00 | 00 | 00 | 00 | 00 | 00 | 00 | 00 | 00 | 00 | 00 | 00 | -| ::4.1.B. | 00 | 00 | 00 | 00 | 00 | 00 | 00 | 00 | 00 | 00 | 00 | 00 | 00 | -| ::4.1.C. | 00 | 00 | 00 | 00 | 00 | 00 | 00 | 00 | 00 | 00 | 00 | 00 | 00 | -| ::4.1.D. | 00 | 00 | 00 | 00 | 00 | 00 | 00 | 00 | 00 | 00 | 00 | 00 | 00 | -| ::4.2. | 00 | 00 | 00 | 00 | 00 | 00 | 00 | 00 | 00 | 00 | 00 | 00 | 00 | -| ::5. | 00 | 00 | 00 | 00 | 00 | 00 | 00 | 00 | 00 | 00 | 00 | 00 | 00 | -| ::6. | 00 | 00 | 00 | 00 | 00 | 00 | 00 | 00 | 00 | 00 | 00 | 00 | 00 | -| ::Weekly Totals | 00 | 00 | 00 | 00 | 00 | 00 | 00 | 00 | 00 | 00 | 00 | 00 | 00 | - -### Risk Management - -*TODO: List and rank the major risks of this project, and what you plan -to do to mitigate each risk. If you don't plan to do anything to -mitigate the risk, state that. Use the risk list below, or the [risks -worksheet](risks.html).* - -Please see the [risks worksheet](risks.html). - -#### The main risks of this project are - -1. ::There is a potential conflict between the goals of a high-quality - appearance and one that is completely customizable. We can only - succeed if players find the web site appealing, and game vendors can - customize it with no more effort than would be needed to build a - static website. We already have a design in mind that will address - this risk and we will review it with a web site designer who worked - for a game vendor site. -2. ::There are significant technical difficulties in building a web site - and web application. This will be a risk because one person on our - team has much experience with the relevant tools and technologies. - Although the others will learn, we will certainly make some mistakes - and suboptimal choices. We will address this risk by scoping the - project such that we have enough time to train and to review the - 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 - 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 - our current team members has experience with database optimization. - To address this, we will arrange a review meeting with an - experienced DBA or hire a consultant from the database vendor. -5. ::We could be underestimating known tasks. HOW TO AVOID/MITIGATE? -6. ::We could be underestimating the impact of unknown tasks. HOW TO - AVOID/MITIGATE? -7. ::We could be underestimating the dependencies between tasks. HOW TO - AVOID/MITIGATE? -8. ::We could have misunderstood the customer's requirements. HOW TO - AVOID/MITIGATE? -9. ::The customer could change the requirements. HOW TO AVOID/MITIGATE? -10. ::We could face major difficulties with the technology chosen for - this project. HOW TO AVOID/MITIGATE? -11. ::We could have low quality that demands significant rework. HOW TO - AVOID/MITIGATE? -12. ::We could incorrectly assess our progress until it is too late - to react. HOW TO AVOID/MITIGATE? -13. ::We could lose resources. E.g., team members could get sick, spend - time on other projects, or quit. HOW TO AVOID/MITIGATE? -14. ::There may be a mis-alignment of stakeholder goals or expectations. - HOW TO AVOID/MITIGATE? - -### Project Planning Dependencies -&nbsp; -#### Does this project conflict or compete for resources with any other project? - -::No, this is the only project that we are working on. - -::Yes, and we have determined how many hours each person can actually - dedicate to this project. - -#### Are the same human or machine resources allocated to maintenance of past versions and/or planning of future versions during this release time period? - -::No, this is the first release and we will not plan the next release. - -::Yes, we predict that team members will spend an average of 20% of - their time maintaining previous releases and planning future - releases during this release time frame. Some weeks may be higher if - an urgent patch to a previous release is needed. - -#### Does this project depend on the success of any other project? - -::No, this project stands alone. - -::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? - -::No, project is not producing any components that will be used in -other current projects. - -::Yes, we must produce library L for our project and support users of -L in projects P1 and P2. - -#### Are there any other important dependencies that will affect this project? - -::No, everything is covered above. - -::Yes. DETAILS.... - -<!-- End Markdown content --> - - -
-
- - - - - - - - - - - - diff --git a/Project-Plan.md b/Project-Plan.md index 35b1de6..c3c61ab 100644 --- a/Project-Plan.md +++ b/Project-Plan.md @@ -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 + 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 +| 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 +*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 + 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 +::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.... - - ---- -***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.* diff --git a/Proposal.md b/Proposal.md index eb108b8..7dcc473 100644 --- a/Proposal.md +++ b/Proposal.md @@ -22,7 +22,7 @@ # Project Proposal --- ##### Project: - ::[PROJECTNAME](index.html) + ::[PROJECTNAME]">Readyset GFM ##### Project Time-frame: ::2003/1/16 to 2003/3/19 diff --git a/QA-Plan.md b/QA-Plan.md index f97dd61..b431a23 100644 --- a/QA-Plan.md +++ b/QA-Plan.md @@ -27,7 +27,7 @@ questions. In cases where multiple answers are already written, delete those answers that do not apply.* ##### Project: -::[PROJECTNAME](index.html) +::[PROJECTNAME]">Readyset GFM ##### Internal Release Number:: ::X.Y.Z diff --git a/Release-Checklist.md b/Release-Checklist.md index 0b675fd..cd7936a 100644 --- a/Release-Checklist.md +++ b/Release-Checklist.md @@ -27,7 +27,7 @@ questions. In cases where multiple answers are already written, delete those answers that do not apply.* ##### Project: -::[PROJECTNAME](index.html) +::[PROJECTNAME]">Readyset GFM ##### Internal Release Number: ::X.Y.Z diff --git a/Resource-Needs.md b/Resource-Needs.md index 41cdab3..feb9d91 100644 --- a/Resource-Needs.md +++ b/Resource-Needs.md @@ -23,7 +23,7 @@ --- ##### Project: -::[PROJECTNAME](index.html) +::[PROJECTNAME]">Readyset GFM ##### Internal Release Number: ::X.Y.Z diff --git a/Review-Meeting-Notes.md b/Review-Meeting-Notes.md index 4606587..de71665 100644 --- a/Review-Meeting-Notes.md +++ b/Review-Meeting-Notes.md @@ -23,7 +23,7 @@ --- ##### Project: -::[PROJECTNAME](index.html) +::[PROJECTNAME]">Readyset GFM ##### Release Number: ::X.Y.Z diff --git a/Risks.md b/Risks.md index 880e52e..197accd 100644 --- a/Risks.md +++ b/Risks.md @@ -23,7 +23,7 @@ --- ##### Project: -::[PROJECTNAME](index.html) +::[PROJECTNAME]">Readyset GFM ##### Internal Release Number ::X.Y.Z diff --git a/Status-Report.md b/Status-Report.md index 2a3cd00..6120648 100644 --- a/Status-Report.md +++ b/Status-Report.md @@ -30,7 +30,7 @@ available.* examples are given, you should select/edit only one.* ##### Project: -::[PROJECTNAME](index.html) +::[PROJECTNAME]">Readyset GFM ##### Status Report Date: ::YEAR/MONTH/DAY diff --git a/Summary.md b/Summary.md index 76e7fcc..4e70c50 100644 --- a/Summary.md +++ b/Summary.md @@ -1,7 +1,7 @@ ### Mission and Scope *TODO: Answer these questions in your own words. This is condensed -from the project [overview](index.html).* +from the project [Home](Home).* #### What problem does this project address? ::2-4 SENTENCE PROBLEM diff --git a/Test-Run-Suite.md b/Test-Run-Suite.md index 540f1bf..b3cb2fd 100644 --- a/Test-Run-Suite.md +++ b/Test-Run-Suite.md @@ -23,7 +23,7 @@ --- ##### Project: -::[PROJECTNAME](index.html) +::[PROJECTNAME]">Readyset GFM ##### Internal Release Number: ::X.Y.Z diff --git a/Test-Runs.md b/Test-Runs.md index a5dce97..151ff63 100644 --- a/Test-Runs.md +++ b/Test-Runs.md @@ -23,7 +23,7 @@ --- ##### Project: -::[PROJECTNAME](index.html) +::[PROJECTNAME]">Readyset GFM ##### Internal Release Number: ::X.Y.Z diff --git a/Test-Suite.md b/Test-Suite.md index dc1936e..6b4ae72 100644 --- a/Test-Suite.md +++ b/Test-Suite.md @@ -23,7 +23,7 @@ --- ##### Project: -::[PROJECTNAME](index.html) +::[PROJECTNAME]">Readyset GFM ##### Internal Release Number: ::X.Y.Z diff --git a/Use-Case-Suite.md b/Use-Case-Suite.md index b07e1b1..16a2c4d 100644 --- a/Use-Case-Suite.md +++ b/Use-Case-Suite.md @@ -23,7 +23,7 @@ --- ##### Project: -::[PROJECTNAME](index.html) +::[PROJECTNAME]">Readyset GFM ##### Internal Release Number: ::X.Y.Z diff --git a/User-Needs.md b/User-Needs.md index 3f31479..b074966 100644 --- a/User-Needs.md +++ b/User-Needs.md @@ -23,7 +23,7 @@ --- ##### Project: -::[PROJECTNAME](index.html) +::[PROJECTNAME]">Readyset GFM ##### Attached worksheets: - User needs > [Interview notes](interview-notes.html) diff --git a/Workflows.md b/Workflows.md index 02b07c7..e5fd143 100644 --- a/Workflows.md +++ b/Workflows.md @@ -1,6 +1,6 @@ ### By Activity 1. Project Planning - 1. [Overview](index.html) + 1. [Home](Home) 2. [Proposal](proposal.html) - [Target and benefits](target-and-benefits.html) 3. [Project plan](plan.html) @@ -41,7 +41,7 @@ ### By Suggested Sequence 1. Step 1 - 1. [Overview](index.html) + 1. [Home](Home) 2. [Proposal](proposal.html) - [](target-and-benefits.html)[Target and benefits](target-and-benefits.html) 3. [Project plan](plan.html) @@ -82,7 +82,7 @@ ### All Templates 1. [All-in-one](all-in-one.html) -2. [Overview](index.html) +2. [Home](Home) 3. [Proposal](proposal.html) - [Target and benefits](target-and-benefits.html) 4. [Project plan](plan.html)