Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Date

Attendees

Goals

Discussion items

...

Action items

  •  

This is the piece of the TC Charter that we are discussing:

  • Long term strategic Architectural Blueprint - updated with each major release

    • defines the technical strategy for the platform beyond the current major release targeted by development

    • serves as a guideline to ensure that “local decision making” by development teams remains compatible with long term visions

    • accounts for strategic directions beyond the current scope of the platform.  

We decided that we need to add this to our charter:

  • An Architectural Roadmap 

What's the purpose of the Architectural Blueprint

  • Needs to support the PC roadmap
  • Answer the question how the platform does (or doesn't) do something
  • Serves as a guideline to ensure that “local decision making” by development teams remains compatible with long term visions

Who is the audience for this?

  • New Developers/teams
  • Existing Developers/teams
  • Adopters
  • Service Providers







What should go into an Architectural Roadmap?

How does it relate to Tech Debt? Should it have Best practices?



How is it different/compliment the PC Feature Roadmap?

What's the timeframe that should be covered?