A collection of resources to challenge our thinking about what we need our digital services to do. To help us to see the software and infrastructure needed to help manage business risk.
Many projects have a good grip on the functional requirements. These user needs are shared across a cross disciplined group which can then collaborate to discover and build a service.
The Cross (or Non) Functional Requirements - the requirements that support the user needs at scale - often get forgotten, ignored or not valued.
Like the functional requirements, the Cross Functional Requirements should be understood and owned by a wide group.
I've started making less statements and asking different, less technical focused, questions so we can all prioritise and plan together.
These slides present a set of questions that are worth asking when developing a new service or replacing an existing one. I've written open questions without technical jargon, with a view of starting as wide a conversation as possible.
It's written in Remark and should be easily viewed through most browsers. (It seems to also behave well when printed, but let me know if other formats would be useful.)
I'm sure they aren't complete, or perfect. How about a fork and a pull request?
Look into the near future, using this set of questions to explore the cross-functional needs of a project. Ask what's likely to happen and explore what we will need to do to manage the impact and risk.
This Mural board lays out the structure for a discovery session.
Gather as a group, ensure everyone is aware of the work to be discussed, pick 3 cards and begin!
There is more detail on session format here: The Pre-Mortum Workshop