A - Tips on req42 Sections

Section 01: Business Goals 11
Section 02: Stakeholders 4
Section 03: Scope1
Section 04: Product Backlog 0
Section 05: Supporting Models 4
Section 06: Quality Requirements 7
Section 07: Constraints 2
Section 08: Domain Terminology 0
Section 09: Assets 0
Section 10: Teams 0
Section 11: Roadmap 0
Section 12: Risks / Assumptions 3

Section 01: Business Goals

Tip A-1-01: Never start a product development or project without goals.

#clean-start

Tip A-1-02: Deadlines and budget limits are not goals, but constraints.

#constraints

Tip A-1-03: You should never have more than a handful of goals for a product.

#clean-start

Tip A-1-04: Clarify conflicting goals before getting lost in the details of requirements.

#goals

Tip A-1-05: Visions and business goals need a time horizon.

#goals

Tip A-1-06: Only in very large projects should you distinguish visions and business goals.

Tip A-1-07: Work with nested goal trees for very large projects.

Tip A-1-08: You do not need to put sprint goals in writing.

Tip A-1-09: Save the effort of separating visions from goals.

#goals
#lean

Tip A-1-10: Make goals measurable.

#acceptance-criteria

Tip A-1-11: Save on the PAM formulation of goals.

Section 02: Stakeholders

Tip A-2-01: Conduct a breadth search for stakeholders.

#stakeholder

Tip A-2-02: Role before person.

#stakeholder

Tip A-2-03: Iterate: Critically review stakeholder table again and again.

#stakeholder

Tip A-2-04: Classify your stakeholders by interest and influence.

#stakeholder

Section 03: Scope

Tip A-3-01: Explicitly define the boundary between your product and its environment!

Section 04: Product Backlog

Section 05: Supporting Models

Tip A-5-01: Use use case models.

#use-cases

Tip A-5-02: Use activity diagrams to refine epics or use cases.

#activity-diagrams

Tip A-5-03: Use coarse data models to arrive at a unified domain language.

Tip A-5-04: Use more precise data models.

Section 06: Quality Requirements

Tip A-6-01: Always work with explicit quality requirements.

#scenarios

Tip A-6-02: Quality requirements are the architecture drivers.

#scenarios

Tip A-6-03: Use checklists to get ideas for topics for which you should collect explicit quality requirements.

#checklist

Tip A-6-04: Use Q42's 150+ quality attributes as a starting point to find sample formulations that you can copy or adapt.

Tip A-6-05: Never argue about whether a requirement is a functional requirement or a quality requirement.

#requirements-categorization

Tip A-6-06: Focus on the 'killer qualities' early in the project.

Tip A-6-07: Take advantage of the property that quality requirements are highly reusable within a domain.

Section 07: Constraints

Tip A-7-01: Look for constraints in other projects within your organization.

Tip A-7-02: Never argue about whether a requirement is a quality requirement or a constraint.

#categorization

Section 08: Domain Terminology

}

Section 09: Assets

Section 10: Teams

Section 11: Roadmap

Section 12: Risks / Assumptions

Tip A-12-01: Search for risks with different stakeholders

#stakeholder

Tip A-12-02: Analyze external interfaces for risks

#Interfaces

Tip A-12-03: Enrich your risk list with probabilites and

#risks