#bradleyquartet — Public Fediverse posts

#BradleyQuartet #BQ in a nutshell (primer):

1. What problem?
2. Why problem?
3. What solution?
4. Why solution? (Prove to neutral, 3rd party standard)

That's scope, rationale, ideation, and acceptance.

It keeps the business upstairs.
It keeps the tech downstairs.
It keeps the data centered.
Which keeps things on the rails.

Syllabus and course-ware available, too.

I refactored that '4 Part Problem' to make it fit for purpose as a drop in that can work anywhere, scalable.

I'll prove it.🖖

#BradleyQuartet #BQ in a nutshell (primer):

1. What problem?
2. Why problem?
3. What solution?
4. Why solution? (Prove to neutral, 3rd party standard)

That's scope, rationale, ideation, and acceptance.

It keeps the business upstairs.
It keeps the tech downstairs.
It keeps the data centered.
Which keeps things on the rails.

Syllabus and course-ware available, too.

I refactored that '4 Part Problem' to make it fit for purpose as a drop in that can work anywhere, scalable.

I'll prove it.🖖

#BradleyQuartet #BQ in a nutshell (primer):

1. What problem?
2. Why problem?
3. What solution?
4. Why solution? (Prove to neutral, 3rd party standard)

That's scope, rationale, ideation, and acceptance.

It keeps the business upstairs.
It keeps the tech downstairs.
It keeps the data centered.
Which keeps things on the rails.

Syllabus and course-ware available, too.

I refactored that '4 Part Problem' to make it fit for purpose as a drop in that can work anywhere, scalable.

I'll prove it.🖖

#BradleyQuartet #BQ in a nutshell (primer):

1. What problem?
2. Why problem?
3. What solution?
4. Why solution? (Prove to neutral, 3rd party standard)

That's scope, rationale, ideation, and acceptance.

It keeps the business upstairs.
It keeps the tech downstairs.
It keeps the data centered.
Which keeps things on the rails.

Syllabus and course-ware available, too.

I refactored that '4 Part Problem' to make it fit for purpose as a drop in that can work anywhere, scalable.

I'll prove it.🖖

#BradleyQuartet #BQ in a nutshell (primer):

1. What problem?
2. Why problem?
3. What solution?
4. Why solution? (Prove to neutral, 3rd party standard)

That's scope, rationale, ideation, and acceptance.

It keeps the business upstairs.
It keeps the tech downstairs.
It keeps the data centered.
Which keeps things on the rails.

Syllabus and course-ware available, too.

I refactored that '4 Part Problem' to make it fit for purpose as a drop in that can work anywhere, scalable.

I'll prove it.🖖

I am bemused by the ongoing holy wars over points, estimates, slicing, dicing, julienne, RONCO....

I built and use a method (since 1992) that eliminates the need for any of that, slots easily into XP, TDD, FDD, BDD, Scrum, Agile, or anywhere else.

Four questions. Automagical full story with criteria that is effectively unbreakable and simultaneously at lowest level of complexity (task > operation > procedure > process > policy is the linkage).

It's called the #BradleyQuartet or #BQ. 🖖

I am bemused by the ongoing holy wars over points, estimates, slicing, dicing, julienne, RONCO....

I built and use a method (since 1992) that eliminates the need for any of that, slots easily into XP, TDD, FDD, BDD, Scrum, Agile, or anywhere else.

Four questions. Automagical full story with criteria that is effectively unbreakable and simultaneously at lowest level of complexity (task > operation > procedure > process > policy is the linkage).

It's called the #BradleyQuartet or #BQ. 🖖

I am bemused by the ongoing holy wars over points, estimates, slicing, dicing, julienne, RONCO....

I built and use a method (since 1992) that eliminates the need for any of that, slots easily into XP, TDD, FDD, BDD, Scrum, Agile, or anywhere else.

Four questions. Automagical full story with criteria that is effectively unbreakable and simultaneously at lowest level of complexity (task > operation > procedure > process > policy is the linkage).

It's called the #BradleyQuartet or #BQ. 🖖

I am bemused by the ongoing holy wars over points, estimates, slicing, dicing, julienne, RONCO....

I built and use a method (since 1992) that eliminates the need for any of that, slots easily into XP, TDD, FDD, BDD, Scrum, Agile, or anywhere else.

Four questions. Automagical full story with criteria that is effectively unbreakable and simultaneously at lowest level of complexity (task > operation > procedure > process > policy is the linkage).

It's called the #BradleyQuartet or #BQ. 🖖

I am bemused by the ongoing holy wars over points, estimates, slicing, dicing, julienne, RONCO....

I built and use a method (since 1992) that eliminates the need for any of that, slots easily into XP, TDD, FDD, BDD, Scrum, Agile, or anywhere else.

Four questions. Automagical full story with criteria that is effectively unbreakable and simultaneously at lowest level of complexity (task > operation > procedure > process > policy is the linkage).

It's called the #BradleyQuartet or #BQ. 🖖