Change Details

==== Background/Goal Understand and prioritize the known use cases and tasks required for a successful RESTbase deprecation. This task will focus on how, when, and why work should be developed, rather than actually developing the features. ==== User stories [] As an API Platform team member, I need to know what are the priority tasks related to RESTbase deprecation, so I can work on achievable sequential parts that ladder up to the overall successful completion of project. [] As an engineer with RESTbase related dependencies, I can efficiently follow the progress, so I can plan my tasks according to dependencies. ==== Considerations - What capabilities are critical vs nice-to-have? - What capabilities have the biggest impact? - What capabilities have the most dependencies? - How can we scope this work in a way that delivers incremental benefits? ==== Requirements **For each infrastructure capability, draft a potential proposal that includes: ** [] A brief description of what the use case is [] Bullet list of potential/expected end-user impacts (both positive and negative) [] Bullet other internal/external impacts [] List of what this blocks (if anything) and why. Include examples. [] Work Breakdown structure [] Documents links to existing artifacts, tickets, etc. [] Open questions/additional areas to explore **Upon completion of the above:** [] Tech Lead & Engineering Manager review [] Bullet list of what the related infrastructure capabilities are [] Bullet list of potential/expected development/engineering impacts (both positive and negative) [] Bullet list of potential/expected design impacts (both positive and negative) [] Describe WHAT phases or chunks of work could be done and by WHO [] List any dependencies we have on any tools, teams, etc. [] Meeting set to review scope with Product Manager [] Once scope completed and agreed to, next steps defined (ex: create Epic w/ subtasks) ====Acceptance criteria [] It is clear to see how the target capability impacts end-users [] It is clear how the target capability impacts WMF staff [] Impact can be delivered incrementally, without having to wait months or to the end of a project to see impact [] Non-technical audiences can understand why this work matters and how it impacts the community ====Test scenarios [to come] ====Open questions [to come]

==== Background/Goal Understand and prioritize the known use cases and tasks required for a successful RESTbase deprecation. This task will focus on how, when, and why work should be developed, rather than actually developing the features. ==== User stories [] As an API Platform team member, I need to know what are the priority tasks related to RESTbase deprecation, so I can work on achievable sequential parts that ladder up to the overall successful completion of project. [] As an engineer with RESTbase related dependencies, I can efficiently follow the progress, so I can plan my tasks according to dependencies. ==== Considerations - What capabilities are critical vs nice-to-have? - What capabilities have the biggest impact? - What capabilities have the most dependencies? - How can we scope this work in a way that delivers incremental benefits? ==== Requirements **For each infrastructure capability, draft a potential proposal that includes: ** [] A brief description of what the use case is [] Bullet list of potential/expected end-user impacts (both positive and negative) [] Bullet other internal/external impacts [] List of what this blocks (if anything) and why. Include examples. [] Work Breakdown structure [] Documents links to existing artifacts, tickets, etc. [] Open questions/additional areas to explore **Upon completion of the above:** [] Tech Lead & Engineering Manager review [] Bullet list of what the related infrastructure capabilities are [] Bullet list of potential/expected development/engineering impacts (both positive and negative) [] Bullet list of potential/expected design impacts (both positive and negative) [] Describe WHAT phases or chunks of work could be done and by WHO [] List any dependencies we have on any tools, teams, etc. [] Meeting set to review scope with Product Manager [] Once scope completed and agreed to, next steps defined (ex: create Epic w/ subtasks) ====Acceptance criteria [] It is clear to see how the target capability impacts end-users [] It is clear how the target capability impacts WMF staff [] Impact can be delivered incrementally, without having to wait months or to the end of a project to see impact [] Non-technical audiences can understand why this work matters and how it impacts the community ====Links [[ https://docs.google.com/spreadsheets/d/1NiK6TrdzNxhXPVwaFMZLw39WdlVxv4bmZ3Y1irbxYA0/edit#gid=0 | RESTbase Deprecation/Sunsetting Work Breakdown ]]

==== Background/Goal Understand and prioritize the known use cases and tasks required for a successful RESTbase deprecation. This task will focus on how, when, and why work should be developed, rather than actually developing the features. ==== User stories [] As an API Platform team member, I need to know what are the priority tasks related to RESTbase deprecation, so I can work on achievable sequential parts that ladder up to the overall successful completion of project. [] As an engineer with RESTbase related dependencies, I can efficiently follow the progress, so I can plan my tasks according to dependencies. ==== Considerations - What capabilities are critical vs nice-to-have? - What capabilities have the biggest impact? - What capabilities have the most dependencies? - How can we scope this work in a way that delivers incremental benefits? ==== Requirements **For each infrastructure capability, draft a potential proposal that includes: ** [] A brief description of what the use case is [] Bullet list of potential/expected end-user impacts (both positive and negative) [] Bullet other internal/external impacts [] List of what this blocks (if anything) and why. Include examples. [] Work Breakdown structure [] Documents links to existing artifacts, tickets, etc. [] Open questions/additional areas to explore **Upon completion of the above:** [] Tech Lead & Engineering Manager review [] Bullet list of what the related infrastructure capabilities are [] Bullet list of potential/expected development/engineering impacts (both positive and negative) [] Bullet list of potential/expected design impacts (both positive and negative) [] Describe WHAT phases or chunks of work could be done and by WHO [] List any dependencies we have on any tools, teams, etc. [] Meeting set to review scope with Product Manager [] Once scope completed and agreed to, next steps defined (ex: create Epic w/ subtasks) ====Acceptance criteria [] It is clear to see how the target capability impacts end-users [] It is clear how the target capability impacts WMF staff [] Impact can be delivered incrementally, without having to wait months or to the end of a project to see impact [] Non-technical audiences can understand why this work matters and how it impacts the community ====Test scenarios [to come] ====Open questions [to come]Links [[ https://docs.google.com/spreadsheets/d/1NiK6TrdzNxhXPVwaFMZLw39WdlVxv4bmZ3Y1irbxYA0/edit#gid=0 | RESTbase Deprecation/Sunsetting Work Breakdown ]]