Requirements path refinements workshop v3 1

Requirements Management Refinement & Enhancement

Agenda1.Problem Statements

2.Requirements Management and SDLC

3.Walkthrough (WT) Process

4.Feedback Mechanics

5.Signoff Process

Problem Statements• Walkthrough process is ambiguous

• Feedback mechanics are unclear

• Signoff process accountabilities and definition requires clarity

RM & SDLC

Walkthrough• Walkthrough

• What is a reasonable lead time for review?

• Who needs to participate?• Prod, Arch, Dev, QA, TA, IT?• CTPS, Marketing, Sales, PMO?

• What does their participation mean?

• Train the Trainer?

• Budgeting impacts…

• When is a second Walkthrough required?

Walkthrough - Recommendations• Walkthrough recommendations

• ** Participants must come prepared **• 5 business days lead time for work package review

• Standard Rule of Thumb, but can be amended by project group (active vs. passive changes)

• Participants (Rule of Thumb)• BRD Walkthrough Mandatory: Prod/BS, Arch, Dev, QA• FSD Walkthrough Mandatory: Prod/BS, Arch, Dev, QA, TA, • Optional: TA, IT, CTPS, Marketing, Sales?

• Budget Management• 1 attendee from each group assigned and accountable• Other attendees non-billable?

• When is a second Walkthrough required?• Material impacts/changes to artifact only• Should be determined at the end of walkthrough

Feedback Mechanics• Feedback Mechanics

• What is a reasonable timeframe for feedback?

• Who should the feedback go to?

• What is a reasonable timeframe for revisions?

Feedback Mechanics - Recommendations• Feedback Mechanics

• 2 business days to provide feedback from signatory groups• Feedback should go to Author and Project Manager only

• Author will publish aggregate feedback back to team

• 5 business days for revisions unless otherwise noted• Revisions are sent as an FYI (final) unless material impact to

Requirements or Design

• Only material changes result in a second walkthrough• Determined by project group

Signoff Process • What does signoff really mean?

– Do different phases have different processes?

– Accountabilities & Signatories?– BRD signoff – who signs off?– FSD signoff – who signs off?– Prod, Arch, Dev, QA, TA, IT?– CTPS, Marketing, Sales, PMO?

Signoff Process - Recommendation• Signoff means the work package received is complete and

accurate for functional group to start its next deliverable • (tech spec, test strategy etc.)

• Signoff within 2 business days of receipt of revised (or final) work package • unless a 2nd walkthrough is required

• BRD signoff • Mandatory: Product/BS, Arch, QA, Client (if applicable)• Optional: Dev?

• FSD signoff• Mandatory: Product/BS, Arch, Dev, QA • Optional: TA? IT?