A Better Way to Build Software Programs

This is a better way of approaching complex enterprise software and digital programs.

I am incubating a new workshop for software companies that is focused on non-functional requirements. If your MVP is 50% of your pitch, this will make your MVP 99% better.

People spend a lot of time on functional requirements, but they think less about non-functional requirements. They tend to assume that software framework selection and integration in a program will satisfy their non-functional needs. That is true to some extent, but “Which framework will you choose, and why?” is a big question. This approach can help you select your framework.

One advantage of this thinking is that it is easy to build NFRs into your software at the beginning of its life, but extremely expensive to re-engineer them after you have customers.

Even thinking of these NFRs as part of design will help your software developers make better choices, including when some of the features are stubbed out in the MVP.

It is an Ironstone Pattern of Success to assess your NFRs. We advise using NFR principles in program creation in this software-driven world.

“If it was fun and easy, there would be sand on the ground and toys everywhere.” — Ernest Hursh

NON-FUNCTIONAL REQUIREMENTS PATTERNS

• Self-Service

• Know Your Customer

• Share Everywhere

• Educate, Educate, Educate

• All Pillars of Observability

• Dynamic Dashboards and Living Notebooks

• Ambient Findability

• Transformations Are All You Need

• AI First, APIs, Headless, Transparent Layers, Cloud and SOMOCLO

• Event-Driven, Content-Powered, Influencer-Amplified Programs

• Blueprints, Diagrams, Canvases — the One-Pagers

Email rob@ironstoneadvisory.com for early access to the workshop work in progress.