Change Log + Future Work: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
m (Marcin moved page Future Work to Change Log + Future Work over redirect) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
= | =Change Log + Future Work Guidelines= | ||
#Click on ProjectName_Change Log + Future_Work in the work product column of the Development Template - to start documenting | |||
#Click on ProjectName_Change Log + Future_Work to start documenting | |||
#'''Start with all the changes that have been made or suggested during the design/build/engineering cycle.''' There are always new insights that come up during cycles - and these should be documented so that someone can track the evolution of any given project or product. There is no limit to how far this can go, in the spirit of continuous improvement. | #'''Start with all the changes that have been made or suggested during the design/build/engineering cycle.''' There are always new insights that come up during cycles - and these should be documented so that someone can track the evolution of any given project or product. There is no limit to how far this can go, in the spirit of continuous improvement. | ||
#Document relevant suggestions for future work or improvements based on data collection. The Future Work should include: | #Document relevant suggestions for future work or improvements based on data collection. The Future Work should include: | ||
##Next steps as informed by results from a build - such as improvements, eliminations of unnecessary features, additions of features, etc. | ##Next steps as informed by results from a build - such as improvements, eliminations of unnecessary features, additions of features, etc. | ||
##A proposed roadmap - for the short and long term - identifying development points and valuable directions uncovered as a result of data collection.}} | ##A proposed roadmap - for the short and long term - identifying development points and valuable directions uncovered as a result of data collection.}} | ||
Latest revision as of 13:12, 5 December 2025
Change Log + Future Work Guidelines
- Click on ProjectName_Change Log + Future_Work in the work product column of the Development Template - to start documenting
- Start with all the changes that have been made or suggested during the design/build/engineering cycle. There are always new insights that come up during cycles - and these should be documented so that someone can track the evolution of any given project or product. There is no limit to how far this can go, in the spirit of continuous improvement.
- Document relevant suggestions for future work or improvements based on data collection. The Future Work should include:
- Next steps as informed by results from a build - such as improvements, eliminations of unnecessary features, additions of features, etc.
- A proposed roadmap - for the short and long term - identifying development points and valuable directions uncovered as a result of data collection.}}