D3.7 Solution requirement specifications and implementation plans

This deliverable is: each development group will formulate requirement specifications per solution, including requirements (what will the system do) and specifications (how will the system do it) and how the solution will be implemented into existing living labs.

How do we see this fitting into an agile software development process? What structure or roadmap can we provide for the cities to agree on what they are building without restricting it’s agile development? Or should this be something we report on once the solution is finished?

I would suggest having these be a living document throughout the software development process, like a mission statement and description for the software.

@JoranVD this is where we were having the conversation about D3.7 before you joined SCORE