From 4b111654ac48c4513c47f2868f14290ae697ed93 Mon Sep 17 00:00:00 2001 From: Evgeny Karasik Date: Tue, 9 Aug 2022 12:43:34 +0300 Subject: [PATCH 01/16] initial draft --- text/450-cdk-public-roadmap.md | 102 +++++++++++++++++++++++++++++++++ 1 file changed, 102 insertions(+) create mode 100644 text/450-cdk-public-roadmap.md diff --git a/text/450-cdk-public-roadmap.md b/text/450-cdk-public-roadmap.md new file mode 100644 index 000000000..4ce9cfa07 --- /dev/null +++ b/text/450-cdk-public-roadmap.md @@ -0,0 +1,102 @@ +# CDK PUBLIC ROADMAP + +* **Original Author(s):**: @evgenyka +* **Tracking Issue**: #450 +* **API Bar Raiser**: @{BAR_RAISER_USER} + +Today, users have a problem when they would like to know the future plans of CDK team. Users need a way to get frequent updates and mid/long term visibility into product roadmap. + +## Working Backwards + +**CHANGELOG** +`BREAKING CHANGE` - the proposed will replace the current process for AWS CDK Roadmap updates. + +**README** +This roadmap is meant to making it easier to communicate with all stakeholders and align on the expected outcomes. Therefore, we prefer to keep it in the same tool and provide an easy and convenient way to get an updates and also update on the progress. +The suggested approach will be: +- Use Issue as a primary entity for the Product Roadmap +- Tag the Product Roadmap issues with "Planning" label for easy search/filtering +- Have two types: + - Half-year roadmap: two issues (January - June, July - December) that will outline the 6 months plans for the team + - Iteration plan: dedicated Issue for each month (an iteration is considered as a month) that outlines what is the focus in each area for this monnt. +- Each issue should be created according to the template (half-year or monthly) + +--- + +Ticking the box below indicates that the public API of this RFC has been +signed-off by the API bar raiser (the `api-approved` label was applied to the +RFC pull request): + +``` +[ ] Signed-off by API Bar Raiser @xxxxx +``` + +## Public FAQ + +Q: who is responsible/in charge of creating and updating the roadmdap? +A: CDK Product Manager is responsible for hal-year updates, any contributer is reponsible to update the iteration plan. + +Q: how frequent the plans will be updated? +A: Iteration plans are reviewed and updated monthly (calendar), half year issue is updated in advance + +Q: how can I influence the roadmap plans? +A: provide your votes and comments in the issue + +### What are we launching today? + +A new process for creating and maintaining the product roadmap. + +### Why should I use this feature? + +To get visibility and information about what are the mid/short term plans of the team. +Provide your inputs, suggestions and comments to the proposed agenda. + +## Internal FAQ +TBD + +### Why are we doing this? + +Current public roadmap is not up to date, which provdies ambiguety for the community. +It is hard to update, hard to review and almost impossible to digest. + +### Why should we _not_ do this? + +We do have current public roadmap, need to invest time and effort to keep it actual. + +### What is the technical solution (design) of this feature? + +- Develop templates for Half-year and iteration roadmap (reflect business goals, domains, challenges, customer feedbacks) +- Product Manager generate half-year roadmap +- Product Manager and contributors create iteration plan +- Contributes and users comment/vote for each + +### Is this a breaking change? + +`BREAKING CHANGE` - the proposed will replace the current AWS CDK Roadmap - https://github.com/orgs/aws/projects/7 + +### What alternative solutions did you consider? + +- Keep Product Roadmap in Project View +- Provide Product Roadmap aside of the tool +- Not providing Roadmap + +### What are the drawbacks of this solution? + +- Content: some internal stuff that is not affecting/impacting the community get exposed +- Discipline: keep process actual +- Review: will require extra effort to review contributers comments, feedbacs and inputs + +### What is the high-level project plan? + +- Get RFC comments and adjust the process +- Develop the templates +- Launch current month update +- Launch half-year update + +### Are there any open issues that need to be addressed later? + +TBD + +## Appendix + +Example: https://github.com/microsoft/TypeScript/labels/Planning \ No newline at end of file From 8087e184a31b82bbf50862f7f33f1bff4674edef Mon Sep 17 00:00:00 2001 From: Evgeny Karasik Date: Tue, 9 Aug 2022 13:45:02 +0300 Subject: [PATCH 02/16] Bare URL fix --- text/450-cdk-public-roadmap.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/text/450-cdk-public-roadmap.md b/text/450-cdk-public-roadmap.md index 4ce9cfa07..89f9a8606 100644 --- a/text/450-cdk-public-roadmap.md +++ b/text/450-cdk-public-roadmap.md @@ -99,4 +99,4 @@ TBD ## Appendix -Example: https://github.com/microsoft/TypeScript/labels/Planning \ No newline at end of file +Example: \ No newline at end of file From 84ef18bb09b9ac4a59183799b6ffef0e2112fb17 Mon Sep 17 00:00:00 2001 From: Evgeny Karasik Date: Tue, 9 Aug 2022 13:49:24 +0300 Subject: [PATCH 03/16] Markdown Changes --- text/450-cdk-public-roadmap.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/text/450-cdk-public-roadmap.md b/text/450-cdk-public-roadmap.md index 89f9a8606..7d4c4eb6a 100644 --- a/text/450-cdk-public-roadmap.md +++ b/text/450-cdk-public-roadmap.md @@ -4,7 +4,8 @@ * **Tracking Issue**: #450 * **API Bar Raiser**: @{BAR_RAISER_USER} -Today, users have a problem when they would like to know the future plans of CDK team. Users need a way to get frequent updates and mid/long term visibility into product roadmap. +Today, users have a problem when they would like to know the future plans of CDK team. +Users need a way to get frequent updates and mid/long term visibility into product roadmap. ## Working Backwards @@ -12,8 +13,10 @@ Today, users have a problem when they would like to know the future plans of CDK `BREAKING CHANGE` - the proposed will replace the current process for AWS CDK Roadmap updates. **README** -This roadmap is meant to making it easier to communicate with all stakeholders and align on the expected outcomes. Therefore, we prefer to keep it in the same tool and provide an easy and convenient way to get an updates and also update on the progress. +This roadmap is meant to making it easier to communicate with the stakeholders and align on the expected outcomes. +Therefore, we prefer to keep it in the same tool and provide an easy and convenient way to get an updates and also update on the progress. The suggested approach will be: + - Use Issue as a primary entity for the Product Roadmap - Tag the Product Roadmap issues with "Planning" label for easy search/filtering - Have two types: @@ -52,6 +55,7 @@ To get visibility and information about what are the mid/short term plans of the Provide your inputs, suggestions and comments to the proposed agenda. ## Internal FAQ + TBD ### Why are we doing this? @@ -72,7 +76,7 @@ We do have current public roadmap, need to invest time and effort to keep it act ### Is this a breaking change? -`BREAKING CHANGE` - the proposed will replace the current AWS CDK Roadmap - https://github.com/orgs/aws/projects/7 +`BREAKING CHANGE` - the proposed will replace the current AWS CDK Roadmap - ### What alternative solutions did you consider? From 4eee326523bf27ecc4b777051339b347339d29b8 Mon Sep 17 00:00:00 2001 From: Evgeny Karasik Date: Tue, 9 Aug 2022 13:53:22 +0300 Subject: [PATCH 04/16] Line spaces --- text/450-cdk-public-roadmap.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/text/450-cdk-public-roadmap.md b/text/450-cdk-public-roadmap.md index 7d4c4eb6a..8558022ad 100644 --- a/text/450-cdk-public-roadmap.md +++ b/text/450-cdk-public-roadmap.md @@ -4,23 +4,23 @@ * **Tracking Issue**: #450 * **API Bar Raiser**: @{BAR_RAISER_USER} -Today, users have a problem when they would like to know the future plans of CDK team. +Today, users have a problem when they would like to know the future plans of CDK team. Users need a way to get frequent updates and mid/long term visibility into product roadmap. ## Working Backwards -**CHANGELOG** +**CHANGELOG** `BREAKING CHANGE` - the proposed will replace the current process for AWS CDK Roadmap updates. **README** -This roadmap is meant to making it easier to communicate with the stakeholders and align on the expected outcomes. +This roadmap is meant to making it easier to communicate with the stakeholders and align on the expected outcomes. Therefore, we prefer to keep it in the same tool and provide an easy and convenient way to get an updates and also update on the progress. The suggested approach will be: - Use Issue as a primary entity for the Product Roadmap - Tag the Product Roadmap issues with "Planning" label for easy search/filtering - Have two types: - - Half-year roadmap: two issues (January - June, July - December) that will outline the 6 months plans for the team + - Half-year roadmap: 2 issues (January - June, July - December) that will outline the 6 months plans for the team - Iteration plan: dedicated Issue for each month (an iteration is considered as a month) that outlines what is the focus in each area for this monnt. - Each issue should be created according to the template (half-year or monthly) @@ -42,12 +42,12 @@ A: CDK Product Manager is responsible for hal-year updates, any contributer is r Q: how frequent the plans will be updated? A: Iteration plans are reviewed and updated monthly (calendar), half year issue is updated in advance -Q: how can I influence the roadmap plans? -A: provide your votes and comments in the issue +Q: how can I influence the roadmap plans? +A: provide your votes and comments in the issue ### What are we launching today? -A new process for creating and maintaining the product roadmap. +A new process for creating and maintaining the product roadmap. ### Why should I use this feature? @@ -88,7 +88,7 @@ We do have current public roadmap, need to invest time and effort to keep it act - Content: some internal stuff that is not affecting/impacting the community get exposed - Discipline: keep process actual -- Review: will require extra effort to review contributers comments, feedbacs and inputs +- Review: will require extra effort to review contributers comments, feedbacs and inputs ### What is the high-level project plan? From 572a107320401c86043815ea403d4f1b4f473418 Mon Sep 17 00:00:00 2001 From: Evgeny Karasik Date: Tue, 9 Aug 2022 13:54:58 +0300 Subject: [PATCH 05/16] New lines --- text/450-cdk-public-roadmap.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/text/450-cdk-public-roadmap.md b/text/450-cdk-public-roadmap.md index 8558022ad..ac56519a9 100644 --- a/text/450-cdk-public-roadmap.md +++ b/text/450-cdk-public-roadmap.md @@ -20,8 +20,8 @@ The suggested approach will be: - Use Issue as a primary entity for the Product Roadmap - Tag the Product Roadmap issues with "Planning" label for easy search/filtering - Have two types: - - Half-year roadmap: 2 issues (January - June, July - December) that will outline the 6 months plans for the team - - Iteration plan: dedicated Issue for each month (an iteration is considered as a month) that outlines what is the focus in each area for this monnt. + - Half-year roadmap: 2 issues (January - June, July - December) that will outline the 6 months plans for the team + - Iteration plan: dedicated Issue for each month (an iteration is considered as a month) that outlines what is the focus in each area for this monnt. - Each issue should be created according to the template (half-year or monthly) --- @@ -103,4 +103,4 @@ TBD ## Appendix -Example: \ No newline at end of file +Example: From 7074c0645f686b028989432075ac9b8fd3b98d8f Mon Sep 17 00:00:00 2001 From: Evgeny Karasik Date: Tue, 9 Aug 2022 13:57:22 +0300 Subject: [PATCH 06/16] new Lines --- text/450-cdk-public-roadmap.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/text/450-cdk-public-roadmap.md b/text/450-cdk-public-roadmap.md index ac56519a9..35617a244 100644 --- a/text/450-cdk-public-roadmap.md +++ b/text/450-cdk-public-roadmap.md @@ -19,9 +19,8 @@ The suggested approach will be: - Use Issue as a primary entity for the Product Roadmap - Tag the Product Roadmap issues with "Planning" label for easy search/filtering -- Have two types: - - Half-year roadmap: 2 issues (January - June, July - December) that will outline the 6 months plans for the team - - Iteration plan: dedicated Issue for each month (an iteration is considered as a month) that outlines what is the focus in each area for this monnt. +- Half-year roadmap: 2 issues (January - June, July - December) that will outline the 6 months plans for the team +- Iteration plan: dedicated Issue for each month (an iteration is considered as a month) that outlines what is the focus in each area for this monnt. - Each issue should be created according to the template (half-year or monthly) --- @@ -104,3 +103,4 @@ TBD ## Appendix Example: + From 7d5a39c23bdb56ea145178e458f59dedb7dd5cee Mon Sep 17 00:00:00 2001 From: Evgeny Karasik Date: Tue, 9 Aug 2022 13:59:12 +0300 Subject: [PATCH 07/16] last line --- text/450-cdk-public-roadmap.md | 1 - 1 file changed, 1 deletion(-) diff --git a/text/450-cdk-public-roadmap.md b/text/450-cdk-public-roadmap.md index 35617a244..25ce36a8a 100644 --- a/text/450-cdk-public-roadmap.md +++ b/text/450-cdk-public-roadmap.md @@ -103,4 +103,3 @@ TBD ## Appendix Example: - From c3e69a0692ba816987f87468e0906f3046d864d9 Mon Sep 17 00:00:00 2001 From: Evgeny Karasik Date: Tue, 9 Aug 2022 17:29:12 +0300 Subject: [PATCH 08/16] Implementing some internal feedbacks --- text/450-cdk-public-roadmap.md | 48 +++++++++++++++++----------------- 1 file changed, 24 insertions(+), 24 deletions(-) diff --git a/text/450-cdk-public-roadmap.md b/text/450-cdk-public-roadmap.md index 25ce36a8a..e063a083c 100644 --- a/text/450-cdk-public-roadmap.md +++ b/text/450-cdk-public-roadmap.md @@ -9,19 +9,20 @@ Users need a way to get frequent updates and mid/long term visibility into produ ## Working Backwards -**CHANGELOG** -`BREAKING CHANGE` - the proposed will replace the current process for AWS CDK Roadmap updates. - -**README** -This roadmap is meant to making it easier to communicate with the stakeholders and align on the expected outcomes. -Therefore, we prefer to keep it in the same tool and provide an easy and convenient way to get an updates and also update on the progress. -The suggested approach will be: - -- Use Issue as a primary entity for the Product Roadmap -- Tag the Product Roadmap issues with "Planning" label for easy search/filtering -- Half-year roadmap: 2 issues (January - June, July - December) that will outline the 6 months plans for the team +**BLOG POST** +Visibility and collaboration are key success eleements for our project. +This roadmap is meant to provide visibility to the community on the plans and expected outcomes and making it easier to communicate with the internal and external stakeholders. +As a contributer or regular user, you will be able to review and understand what are the team plans for the next iteration (1 month) or half year. You will also be able to comment, suggest, vote or complain about the content that is ether planned or currently at work. +You will be also able to understand the prioritization and selection process for the content that is being implemented. +We prefer to have it in the same tool to keep it user-centric and focused. +It should be easy to create, update, understand and respond. +Therefore, the forward-going approach will be: + +- Use Issue as a primary entity for the Product Roadmap. +- Tag the Product Roadmap issues with "Planning" label for easy search/filtering. +- Half-year roadmap: 2 issues (January - June, July - December) that will outline the 6 months plans for the team. - Iteration plan: dedicated Issue for each month (an iteration is considered as a month) that outlines what is the focus in each area for this monnt. -- Each issue should be created according to the template (half-year or monthly) +- The roadmap is focusing on customer value and include innovation and tech debt projects or activities. It is not designed for bug fixes, PR-reviews or any other routine updates. --- @@ -44,6 +45,9 @@ A: Iteration plans are reviewed and updated monthly (calendar), half year issue Q: how can I influence the roadmap plans? A: provide your votes and comments in the issue +Q: I've open a bug, will it be reflected in one of the roadmaps? +A: No, roadmap is reserved for innovation and tech debt increments only. + ### What are we launching today? A new process for creating and maintaining the product roadmap. @@ -59,12 +63,12 @@ TBD ### Why are we doing this? -Current public roadmap is not up to date, which provdies ambiguety for the community. -It is hard to update, hard to review and almost impossible to digest. +Current public roadmap is not up to date, which generates uncertainty for the community. +It is a lot of work to update it, hard to holistically review review it and virtually impossible to respond to it. ### Why should we _not_ do this? -We do have current public roadmap, need to invest time and effort to keep it actual. +We do have current public roadmap, just need to invest in keep it actual and get users feedback. ### What is the technical solution (design) of this feature? @@ -73,20 +77,16 @@ We do have current public roadmap, need to invest time and effort to keep it act - Product Manager and contributors create iteration plan - Contributes and users comment/vote for each -### Is this a breaking change? - -`BREAKING CHANGE` - the proposed will replace the current AWS CDK Roadmap - - ### What alternative solutions did you consider? -- Keep Product Roadmap in Project View -- Provide Product Roadmap aside of the tool -- Not providing Roadmap +- Keep the Product Roadmap in Project View as of today +- Provide Product Roadmap outside of the tool +- Not disclosing the Roadmap ### What are the drawbacks of this solution? -- Content: some internal stuff that is not affecting/impacting the community get exposed -- Discipline: keep process actual +- Content: some internal stuff that is not affecting/impacting the community may get exposed +- Discipline: keep process and information actual and up-to-date - Review: will require extra effort to review contributers comments, feedbacs and inputs ### What is the high-level project plan? From 314ba7ec5b8e9c131a67b6104ec1a82d4cf0fd8b Mon Sep 17 00:00:00 2001 From: Evgeny Karasik Date: Tue, 9 Aug 2022 17:37:59 +0300 Subject: [PATCH 09/16] Format fixes --- text/450-cdk-public-roadmap.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/text/450-cdk-public-roadmap.md b/text/450-cdk-public-roadmap.md index e063a083c..5c646ed05 100644 --- a/text/450-cdk-public-roadmap.md +++ b/text/450-cdk-public-roadmap.md @@ -11,18 +11,19 @@ Users need a way to get frequent updates and mid/long term visibility into produ **BLOG POST** Visibility and collaboration are key success eleements for our project. -This roadmap is meant to provide visibility to the community on the plans and expected outcomes and making it easier to communicate with the internal and external stakeholders. -As a contributer or regular user, you will be able to review and understand what are the team plans for the next iteration (1 month) or half year. You will also be able to comment, suggest, vote or complain about the content that is ether planned or currently at work. +This roadmap is meant to provide visibility to the community on the plans and expected outcomes and making it easier to communicate with the stakeholders. +As a contributer or regular user, you will be able to review and understand what are the team plans for the next iteration (1 month) or half year. +You will also be able to comment, suggest, vote or complain about the content that is ether planned or currently at work. You will be also able to understand the prioritization and selection process for the content that is being implemented. -We prefer to have it in the same tool to keep it user-centric and focused. +We prefer to have it in the same tool to keep it user-centric and focused. It should be easy to create, update, understand and respond. Therefore, the forward-going approach will be: - Use Issue as a primary entity for the Product Roadmap. - Tag the Product Roadmap issues with "Planning" label for easy search/filtering. - Half-year roadmap: 2 issues (January - June, July - December) that will outline the 6 months plans for the team. -- Iteration plan: dedicated Issue for each month (an iteration is considered as a month) that outlines what is the focus in each area for this monnt. -- The roadmap is focusing on customer value and include innovation and tech debt projects or activities. It is not designed for bug fixes, PR-reviews or any other routine updates. +- Iteration plan: dedicated Issue for each and every month (iteration == month) that outlines what is the focus in each area. +- The roadmap is focusing on customer value and include innovation and tech debt projects or activities. It is not designed for bug fixes, PR-reviews or any other routine updates. --- From 261008fcef9b0b13a569fd509c840d7c68fe2260 Mon Sep 17 00:00:00 2001 From: Evgeny Karasik Date: Tue, 9 Aug 2022 17:40:03 +0300 Subject: [PATCH 10/16] Another format fix --- text/450-cdk-public-roadmap.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/text/450-cdk-public-roadmap.md b/text/450-cdk-public-roadmap.md index 5c646ed05..d24e33322 100644 --- a/text/450-cdk-public-roadmap.md +++ b/text/450-cdk-public-roadmap.md @@ -23,7 +23,7 @@ Therefore, the forward-going approach will be: - Tag the Product Roadmap issues with "Planning" label for easy search/filtering. - Half-year roadmap: 2 issues (January - June, July - December) that will outline the 6 months plans for the team. - Iteration plan: dedicated Issue for each and every month (iteration == month) that outlines what is the focus in each area. -- The roadmap is focusing on customer value and include innovation and tech debt projects or activities. It is not designed for bug fixes, PR-reviews or any other routine updates. +- The roadmap is focusing on customer value via innovation and tech debt projects or activities. It is not for bug fixes or PR-reviews updates. --- From 0d0bf47044097dd930a2ed2537a0bc3897f5b34e Mon Sep 17 00:00:00 2001 From: Evgeny Karasik Date: Tue, 9 Aug 2022 17:48:15 +0300 Subject: [PATCH 11/16] Format --- text/450-cdk-public-roadmap.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/text/450-cdk-public-roadmap.md b/text/450-cdk-public-roadmap.md index d24e33322..72beb9c33 100644 --- a/text/450-cdk-public-roadmap.md +++ b/text/450-cdk-public-roadmap.md @@ -23,7 +23,7 @@ Therefore, the forward-going approach will be: - Tag the Product Roadmap issues with "Planning" label for easy search/filtering. - Half-year roadmap: 2 issues (January - June, July - December) that will outline the 6 months plans for the team. - Iteration plan: dedicated Issue for each and every month (iteration == month) that outlines what is the focus in each area. -- The roadmap is focusing on customer value via innovation and tech debt projects or activities. It is not for bug fixes or PR-reviews updates. +- The roadmap is focusing on customer value via innovation and tech debt projects or activities.It is not for bug fixes or PR-reviews updates. --- From 67f5b8c4074a42d992b8e75b8657605edb633812 Mon Sep 17 00:00:00 2001 From: Evgeny Karasik Date: Tue, 9 Aug 2022 18:03:45 +0300 Subject: [PATCH 12/16] First draft for the RFC --- .DS_Store | Bin 0 -> 6148 bytes text/450-cdk-public-roadmap.md | 64 +++++++++++++++++---------------- 2 files changed, 34 insertions(+), 30 deletions(-) create mode 100644 .DS_Store diff --git a/.DS_Store b/.DS_Store new file mode 100644 index 0000000000000000000000000000000000000000..faae9a64b1c36dac8832fd9caaa713d4f6a08147 GIT binary patch literal 6148 zcmeH~F^2|w%k+$f7r}Pn%{oEF$fE17dQa}nw zff*@~$M|YJqi52iNC7D@4+Z@DQ0UH@Y@PAxV2BZb99RzHI%Wy7c!8|R*2xOZa(b|A zwHQOZ9_?hw>uR!f_I6kfAC`AEpJHg%+hK(X&1yhF3P^#80?VF{e*Pcm|IPoC7Nt@^ z3cQ&DHtaw5JHAw&t$$w6>&LA6y3xtFoZ;6`024ooH}o*>7hjMy**aOF=|>=BP>=#I GRp19bPZG)i literal 0 HcmV?d00001 diff --git a/text/450-cdk-public-roadmap.md b/text/450-cdk-public-roadmap.md index 4ce9cfa07..72beb9c33 100644 --- a/text/450-cdk-public-roadmap.md +++ b/text/450-cdk-public-roadmap.md @@ -4,22 +4,26 @@ * **Tracking Issue**: #450 * **API Bar Raiser**: @{BAR_RAISER_USER} -Today, users have a problem when they would like to know the future plans of CDK team. Users need a way to get frequent updates and mid/long term visibility into product roadmap. +Today, users have a problem when they would like to know the future plans of CDK team. +Users need a way to get frequent updates and mid/long term visibility into product roadmap. ## Working Backwards -**CHANGELOG** -`BREAKING CHANGE` - the proposed will replace the current process for AWS CDK Roadmap updates. - -**README** -This roadmap is meant to making it easier to communicate with all stakeholders and align on the expected outcomes. Therefore, we prefer to keep it in the same tool and provide an easy and convenient way to get an updates and also update on the progress. -The suggested approach will be: -- Use Issue as a primary entity for the Product Roadmap -- Tag the Product Roadmap issues with "Planning" label for easy search/filtering -- Have two types: - - Half-year roadmap: two issues (January - June, July - December) that will outline the 6 months plans for the team - - Iteration plan: dedicated Issue for each month (an iteration is considered as a month) that outlines what is the focus in each area for this monnt. -- Each issue should be created according to the template (half-year or monthly) +**BLOG POST** +Visibility and collaboration are key success eleements for our project. +This roadmap is meant to provide visibility to the community on the plans and expected outcomes and making it easier to communicate with the stakeholders. +As a contributer or regular user, you will be able to review and understand what are the team plans for the next iteration (1 month) or half year. +You will also be able to comment, suggest, vote or complain about the content that is ether planned or currently at work. +You will be also able to understand the prioritization and selection process for the content that is being implemented. +We prefer to have it in the same tool to keep it user-centric and focused. +It should be easy to create, update, understand and respond. +Therefore, the forward-going approach will be: + +- Use Issue as a primary entity for the Product Roadmap. +- Tag the Product Roadmap issues with "Planning" label for easy search/filtering. +- Half-year roadmap: 2 issues (January - June, July - December) that will outline the 6 months plans for the team. +- Iteration plan: dedicated Issue for each and every month (iteration == month) that outlines what is the focus in each area. +- The roadmap is focusing on customer value via innovation and tech debt projects or activities.It is not for bug fixes or PR-reviews updates. --- @@ -39,12 +43,15 @@ A: CDK Product Manager is responsible for hal-year updates, any contributer is r Q: how frequent the plans will be updated? A: Iteration plans are reviewed and updated monthly (calendar), half year issue is updated in advance -Q: how can I influence the roadmap plans? -A: provide your votes and comments in the issue +Q: how can I influence the roadmap plans? +A: provide your votes and comments in the issue + +Q: I've open a bug, will it be reflected in one of the roadmaps? +A: No, roadmap is reserved for innovation and tech debt increments only. ### What are we launching today? -A new process for creating and maintaining the product roadmap. +A new process for creating and maintaining the product roadmap. ### Why should I use this feature? @@ -52,16 +59,17 @@ To get visibility and information about what are the mid/short term plans of the Provide your inputs, suggestions and comments to the proposed agenda. ## Internal FAQ + TBD ### Why are we doing this? -Current public roadmap is not up to date, which provdies ambiguety for the community. -It is hard to update, hard to review and almost impossible to digest. +Current public roadmap is not up to date, which generates uncertainty for the community. +It is a lot of work to update it, hard to holistically review review it and virtually impossible to respond to it. ### Why should we _not_ do this? -We do have current public roadmap, need to invest time and effort to keep it actual. +We do have current public roadmap, just need to invest in keep it actual and get users feedback. ### What is the technical solution (design) of this feature? @@ -70,21 +78,17 @@ We do have current public roadmap, need to invest time and effort to keep it act - Product Manager and contributors create iteration plan - Contributes and users comment/vote for each -### Is this a breaking change? - -`BREAKING CHANGE` - the proposed will replace the current AWS CDK Roadmap - https://github.com/orgs/aws/projects/7 - ### What alternative solutions did you consider? -- Keep Product Roadmap in Project View -- Provide Product Roadmap aside of the tool -- Not providing Roadmap +- Keep the Product Roadmap in Project View as of today +- Provide Product Roadmap outside of the tool +- Not disclosing the Roadmap ### What are the drawbacks of this solution? -- Content: some internal stuff that is not affecting/impacting the community get exposed -- Discipline: keep process actual -- Review: will require extra effort to review contributers comments, feedbacs and inputs +- Content: some internal stuff that is not affecting/impacting the community may get exposed +- Discipline: keep process and information actual and up-to-date +- Review: will require extra effort to review contributers comments, feedbacs and inputs ### What is the high-level project plan? @@ -99,4 +103,4 @@ TBD ## Appendix -Example: https://github.com/microsoft/TypeScript/labels/Planning \ No newline at end of file +Example: From c21211faf95cb0129ff9d85cccda2d927dde106b Mon Sep 17 00:00:00 2001 From: Evgeny Karasik Date: Tue, 9 Aug 2022 21:24:58 +0300 Subject: [PATCH 13/16] Grammar and spellcheck --- text/450-cdk-public-roadmap.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/text/450-cdk-public-roadmap.md b/text/450-cdk-public-roadmap.md index 72beb9c33..ef6971312 100644 --- a/text/450-cdk-public-roadmap.md +++ b/text/450-cdk-public-roadmap.md @@ -23,7 +23,7 @@ Therefore, the forward-going approach will be: - Tag the Product Roadmap issues with "Planning" label for easy search/filtering. - Half-year roadmap: 2 issues (January - June, July - December) that will outline the 6 months plans for the team. - Iteration plan: dedicated Issue for each and every month (iteration == month) that outlines what is the focus in each area. -- The roadmap is focusing on customer value via innovation and tech debt projects or activities.It is not for bug fixes or PR-reviews updates. +- The roadmap is focusing on customer value via innovation and tech debt projects or activities.It is not for bug fixes or PR-review updates. --- From 8ff0243c254dbeb16303bb18c1086352cd3b1b1e Mon Sep 17 00:00:00 2001 From: Evgeny Karasik Date: Tue, 9 Aug 2022 21:26:08 +0300 Subject: [PATCH 14/16] Update 450-cdk-public-roadmap.md --- text/450-cdk-public-roadmap.md | 26 +++++++++++++------------- 1 file changed, 13 insertions(+), 13 deletions(-) diff --git a/text/450-cdk-public-roadmap.md b/text/450-cdk-public-roadmap.md index ef6971312..01a819170 100644 --- a/text/450-cdk-public-roadmap.md +++ b/text/450-cdk-public-roadmap.md @@ -4,17 +4,17 @@ * **Tracking Issue**: #450 * **API Bar Raiser**: @{BAR_RAISER_USER} -Today, users have a problem when they would like to know the future plans of CDK team. +Today, users have a problem when they would like to know the future plans of the CDK team. Users need a way to get frequent updates and mid/long term visibility into product roadmap. ## Working Backwards **BLOG POST** -Visibility and collaboration are key success eleements for our project. +Visibility and collaboration are key success elements for our project. This roadmap is meant to provide visibility to the community on the plans and expected outcomes and making it easier to communicate with the stakeholders. -As a contributer or regular user, you will be able to review and understand what are the team plans for the next iteration (1 month) or half year. -You will also be able to comment, suggest, vote or complain about the content that is ether planned or currently at work. -You will be also able to understand the prioritization and selection process for the content that is being implemented. +As a contributor or regular user, you will be able to review and understand what are the team plans for the next iteration (1 month) or half year. +You will also be able to comment, suggest, vote or complain about the content that is either planned or currently at work. +You will also be able to understand the prioritization and selection process for the content that is being implemented. We prefer to have it in the same tool to keep it user-centric and focused. It should be easy to create, update, understand and respond. Therefore, the forward-going approach will be: @@ -37,16 +37,16 @@ RFC pull request): ## Public FAQ -Q: who is responsible/in charge of creating and updating the roadmdap? -A: CDK Product Manager is responsible for hal-year updates, any contributer is reponsible to update the iteration plan. +Q: Who is responsible/in charge of creating and updating the roadmap? +A: CDK Product Manager is responsible for half-year updates, any contributor is responsible to update the iteration plan. -Q: how frequent the plans will be updated? +Q: how frequently will the plans be updated? A: Iteration plans are reviewed and updated monthly (calendar), half year issue is updated in advance Q: how can I influence the roadmap plans? A: provide your votes and comments in the issue -Q: I've open a bug, will it be reflected in one of the roadmaps? +Q: I've opened a bug, will it be reflected in one of the roadmaps? A: No, roadmap is reserved for innovation and tech debt increments only. ### What are we launching today? @@ -65,18 +65,18 @@ TBD ### Why are we doing this? Current public roadmap is not up to date, which generates uncertainty for the community. -It is a lot of work to update it, hard to holistically review review it and virtually impossible to respond to it. +It is a lot of work to update it, hard to holistically review it and virtually impossible to respond to it. ### Why should we _not_ do this? -We do have current public roadmap, just need to invest in keep it actual and get users feedback. +We do have a public roadmap, just need to invest in keeping it actual and get users feedback. ### What is the technical solution (design) of this feature? - Develop templates for Half-year and iteration roadmap (reflect business goals, domains, challenges, customer feedbacks) - Product Manager generate half-year roadmap - Product Manager and contributors create iteration plan -- Contributes and users comment/vote for each +- Contributors and users comment/vote for each ### What alternative solutions did you consider? @@ -88,7 +88,7 @@ We do have current public roadmap, just need to invest in keep it actual and get - Content: some internal stuff that is not affecting/impacting the community may get exposed - Discipline: keep process and information actual and up-to-date -- Review: will require extra effort to review contributers comments, feedbacs and inputs +- Review: will require extra effort to review contributors comments, feedback and inputs ### What is the high-level project plan? From c3039446f6bd9df5bafaa6932945dc102c6cca14 Mon Sep 17 00:00:00 2001 From: Evgeny Karasik Date: Tue, 9 Aug 2022 21:46:35 +0300 Subject: [PATCH 15/16] Update 450-cdk-public-roadmap.md --- text/450-cdk-public-roadmap.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/text/450-cdk-public-roadmap.md b/text/450-cdk-public-roadmap.md index 01a819170..fb3913c94 100644 --- a/text/450-cdk-public-roadmap.md +++ b/text/450-cdk-public-roadmap.md @@ -47,7 +47,7 @@ Q: how can I influence the roadmap plans? A: provide your votes and comments in the issue Q: I've opened a bug, will it be reflected in one of the roadmaps? -A: No, roadmap is reserved for innovation and tech debt increments only. +A: No, Product Roadmap is reserved for innovation and tech debt increments only. ### What are we launching today? From 263f83ee8b0bbedd6a9a81da79c5cddfd5bcf438 Mon Sep 17 00:00:00 2001 From: Evgeny Karasik Date: Tue, 9 Aug 2022 21:56:54 +0300 Subject: [PATCH 16/16] Inspired by --- text/450-cdk-public-roadmap.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/text/450-cdk-public-roadmap.md b/text/450-cdk-public-roadmap.md index fb3913c94..c5b3cde52 100644 --- a/text/450-cdk-public-roadmap.md +++ b/text/450-cdk-public-roadmap.md @@ -103,4 +103,4 @@ TBD ## Appendix -Example: +Inspired by: