At the Increment Planning we also need to have certainty around what the technology stack for a project is going to be. Assuming a new project, this might not be clear and up for a team to decide. Like the Visual Identity step this is only really necessary to do once for the first increment/MVP since subsequent increments would of course build on top of that.
I'm just listing some of the things that come to my mind we'll want to say in that section. This list is not necessarily complete or correct:
there is no one-size-fits-all so we're not recommending any concrete tech stack
obviously a team needs to take into account what kind of technology they already have and how the stack they choose would integrate into that
the team also needs to take into account their capabilities and/or willingness to learn new things
the nature of the project should impact the decision for a technology as well; something that's built to last should be based on tech that is built with sustainability in mind (e.g. Ember.js)
don't look for the latest trends (unless a goal of the project is specifically to explore those of course)
if the project comes with any special challenges (e.g. performance), keep those in mind when choosing technology (e.g. Elixir)
activity level (not necessary size) within the chosen technology's community should be looked at as well – don't want to build on something that's already abandoned
At the Increment Planning we also need to have certainty around what the technology stack for a project is going to be. Assuming a new project, this might not be clear and up for a team to decide. Like the Visual Identity step this is only really necessary to do once for the first increment/MVP since subsequent increments would of course build on top of that.
I'm just listing some of the things that come to my mind we'll want to say in that section. This list is not necessarily complete or correct: