logo

Thông báo

Icon
Error

Chia sẻ
Tùy chọn
Xem
Xem bài viết cuối
Offline admin  
#1 Đã gửi : 06/03/2020 lúc 10:18:35(UTC)
admin

Danh hiệu: Administration

Chức danh:

Nhóm: Administrators
Gia nhập: 23-07-2013(UTC)
Bài viết: 6,115
Man
Viet Nam
Đến từ: Vietnam

Cảm ơn: 10 lần
Được cảm ơn: 2 lần trong 2 bài viết

Hierarchy example:

​​​​​​​

Work Item Type Fields to display:

Fields required for WIT

Start Date

Target Date

Story Points

Effort

Remaining Hours

Priority

Approvers

1EPIC

Y

Y

Y

Y

Y

Y

N
2Feature VersionYYYYYYN
3User StoryYYYYYYY
4Functional RequirementYYYYYYY
5Product TaskYYYYYYN
6Design TaskYYYYYYN
7BSA TaskYYYYYYN
8QA TaskYYYYYYN
9BAT TaskYYYYYYN
10DEV TaskYYYYYYN

Work Item Type: State Details

PhasesPhase 1Phase 2Phase 3-5Phase 6-7Phase 8-9Phase 10Phase 11Phase 12Phase 13

Transition in VSTSNewIn ProgressIn ProgressIn ProgressIn ProgressDoneIn ProgressIn ProgressDoneIn ProgressIn ProgressDoneIn ProgressDoneIn ProgressDoneDone

State

NewActiveUS ReviewUS ApprovedFR ReviewFR ApprovedReady for DevDev In ProgressDev DoneReady for TestingTesting in ProgressTesting DoneIN FBATFBAT DoneIN ABATABAT DoneDone

EPIC

New EPIC is createdNot RequiredNot RequiredNot RequiredNot RequiredNot RequiredNot RequiredNot RequiredNot RequiredNot RequiredNot RequiredNot RequiredNot RequiredNot RequiredNot RequiredNot RequiredNot Required

Condition

No ConditionNo ConditionNo ConditionNo ConditionNo ConditionNo ConditionNo ConditionNo ConditionNo ConditionNo ConditionNo ConditionNo ConditionNo ConditionNo ConditionNo ConditionNo ConditionNo Condition

Feature Version (FV)

New FV is created When FV is assigned to Iteration

FV will transition to this state when US are waiting for Approval. 

FV will transition to this State once US are Approved for all Blocks

FV will transition to this state when FR are waiting for Approval. 

Not RequiredFV will transition to this State once all FR are approved for all Blocks. FV will transition to this State once development starts on any of the US/FR

FV will transition to this state once development is completed on all blocks. 

FV will transition to this State once Development is done for the Block and that Block is ready for testing.

FV will transition to this state once testing starts on any of the testable blocks. 

FV will not move to next state till QA Testing is Done for all Blocks.FV will transition to this state when all blocks are tested and passed QA criteria and feature is ready for Feature BAT.FV will transition to this state when sign off for Feature BAT is received. FV will transition to this state when sign off received for all feature upon Feature BAT completion.FV will transition to this state when sign off for Application level BAT is received. Not Required

Condition

No ConditionOnly PMO transitions this WIT

FV will not move to next state till all US in all blocks are Approved.

Only PMO transitions this WIT

Only PMO transitions this WIT

FV will not move to next state till all FR in all blocks are Approved.

Only PMO transitions this WIT

No ConditionOnly PMO transitions this WITOnly PMO transitions this WIT

FV will not transition to next state till Development is done for all blocks.

Only PMO transitions this WIT

Only PMO transitions this WIT

FV will not transition to next state till all Blocks are tested and pass QA criteria. 

Only PMO transitions this WIT

Only PMO transitions this WITOnly PMO transitions this WIT

FV will not transition to this state until Feature BAT sign off is received.

Only PMO transitions this WIT

Only PMO transitions this WIT

FV will not transition to this state until Application level BAT sign off is received.

Only PMO transitions this WIT

No Condition

User Story (US)

New US is createdWhen US is assigned to IterationWhen US is ready for review and is AWAITING APPROVALOnce US is APPROVED it will automatically transition to APPROVED STATE Not RequiredNot RequiredNot RequiredNot RequiredNot RequiredNot RequiredNot RequiredNot RequiredNot RequiredNot RequiredNot RequiredNot RequiredNot Required

Condition

No ConditionNo Condition

Only US Owner can assign the US to Review State

Only US APPROVERS can REVIEW US and APPROVE/REJECT

Only BSA team can transition US to ACTIVE state in case any EDITS required.

No ConditionNo ConditionNo ConditionNo ConditionNo ConditionNo ConditionNo ConditionNo ConditionNo ConditionNo ConditionNo ConditionNo ConditionNo Condition

Functional Requirements (FR)

New FR is createdWhen FR is assigned to IterationNot RequiredNot Required

When FR is ready for review and is AWAITING APPROVAL

Not RequiredOnce FR is APPROVED it will automatically transition to Ready for DevNot RequiredNot RequiredOnce all the Dev Tasks are done and Functional Requirement is Ready for QA Not RequiredQA has tested against FR and Acceptance criteria is metNot RequiredNot RequiredNot RequiredNot RequiredNot Required

Condition

No ConditionNo ConditionNo ConditionNo Condition

Only FR Owner can assign the FR to Review State

Only FR APPROVERS can REVIEW FR and APPROVE/REJECT

No Condition

Only BSA team can transition FR to ACTIVE state in case any EDITS required.

No ConditionNo ConditionDev Pod Lead will transition this WIT to Ready for QANo ConditionOnly QA can close FRNo ConditionNo ConditionNo ConditionNo ConditionNo Condition

Product Task (PT)

New PT is createdWhen PT is assigned to IterationNot RequiredNot RequiredNot RequiredNot RequiredNot RequiredNot RequiredNot RequiredNot RequiredNot RequiredNot RequiredNot RequiredNot RequiredNot RequiredNot RequiredOnce PT is completed

Condition

No ConditionNo Condition

No Condition

No Condition

No ConditionNo ConditionNo ConditionNo ConditionNo ConditionNo ConditionNo ConditionNo ConditionNo ConditionNo ConditionNo ConditionNo ConditionNo Condition

BSA Task (BSAT)

New BSAT is created When BSAT is assigned to IterationNot RequiredNot RequiredNot RequiredNot RequiredNot RequiredNot RequiredNot RequiredNot RequiredNot RequiredNot RequiredNot RequiredNot RequiredNot RequiredNot RequiredOnce BSAT is completed

Condition

No ConditionNo Condition

No Condition

No Condition

No ConditionNo ConditionNo ConditionNo ConditionNo ConditionNo ConditionNo ConditionNo ConditionNo ConditionNo ConditionNo ConditionNo ConditionNo Condition

Design Task (DT)

New DT is createdWhen DT is assigned to IterationNot RequiredNot RequiredNot RequiredNot RequiredNot RequiredNot RequiredNot RequiredNot RequiredNot RequiredNot RequiredNot RequiredNot RequiredNot RequiredNot RequiredOnce DT is completed

Condition

No ConditionNo Condition

No Condition

No Condition

No ConditionNo ConditionNo ConditionNo ConditionNo ConditionNo ConditionNo ConditionNo ConditionNo ConditionNo ConditionNo ConditionNo ConditionNo Condition

Dev Task (DEVT)

New DEVT is createdNot RequiredNot RequiredNot RequiredNot RequiredNot RequiredNot RequiredWhen DEVT is assigned to IterationOnce DEVT is completedNot RequiredNot RequiredNot RequiredNot RequiredNot RequiredNot RequiredNot RequiredNot Required

Condition

No Condition

No Condition

No Condition

No Condition

No ConditionNo Condition

No Condition

No ConditionNo Condition

No Condition

No Condition

No Condition

No Condition

No Condition

No Condition

No Condition

No Condition

QA Task (QAT)

New QAT is createdNot RequiredNot RequiredNot RequiredNot RequiredNot RequiredNot RequiredNot RequiredNot RequiredNot RequiredWhen QA starts testing against FR/USOnce QAT is completedNot RequiredNot RequiredNot RequiredNot RequiredNot Required

Condition

No Condition

No Condition

No Condition

No Condition

No ConditionNo Condition

No Condition

No Condition

No Condition

No Condition

No ConditionNo Condition

No Condition

No Condition

No Condition

No Condition

No Condition

N/A

Phase 2

Phase 6

Phase 7

Phase 13

1User Story Approval

N/A

N/A

N/AN/A
2Functional Requirement ApprovalN/A

N/A

N/A

3Feature BAT Sign-Off

N/A

N/A

N/A

Teams and Members:

Product Owner

Product Manager

Product Team

User Story Owners

Functional Requirement Owners

BSA Team

BSA Lead

Design Team

Design Lead

BAT Owner

Dev Lead

QA Lead

1Commercial

2Staging

Work Item Type

Description

Estimations (Story Points)

Create (Role to create WIT)

Transition (Role to move WIT)

Close (Role to close WIT)

1EPIC (Feature)

This work item type represent Feature to be released across different releases.

Epic can also be used for tracking Technical Development tasks / QA Tasks 

-

Product Team

Dev / QA Managers

Product Team  / PMO

Dev / QA Managers

PMO

Dev / QA Managers

2Feature Version

This work item type represent Version of the feature to be released.

You can use version number of feature description to identify the feature.

MVP (Dev & QA Lead)Product TeamProduct Team  / PMO

Product Team / PMO

3Group

This work item type represents breakdown of Feature into small testable BLOCKS. 

-Product Team/BSA TeamPMOPMO
4Product TaskThis work item type to be used by Product Team to provide estimates for writing user story.Phase 1 (Product Team)Product TeamPMOPMO
5Design TaskThis work item type to be used by Design Team to provide estimates for LO-FI / HI-FI.Phase 2 (Design Team)Design TeamDesign TeamDesign Team
6BSA TaskThis work item type to be used by BSA Team to provide estimates for writing functional requirementsPhase 2 (BSA Team)BSA TeamBSA TeamBSA Team
7User StoryThis work item type represent User Stories for specific Feature defined under Epic.Phase 3 (Dev & QA Lead)PMOPMO

Automatically transition to Approve State.

Close State not required. 

8Functional RequirementsThis work item type represent Functional Requirements for specific User Story defined under Feature.Phase 9 (Dev & QA Lead)BSA TeamBSA Team

QA will transition this WIT to Testing Done State.

Close State not required. 

9Dev TaskThis work item type to be used by Development team to estimate their work in developing functional requirements.Phase 10 (Dev Team)Dev TeamDev TeamDev Team
10QA Task

This work item type to be used by QA team to estimate feature/acceptance testing under functional requirements

Also to be used for estimating integration testing at the Feature level for all the user stories.

Phase 9 (QA Team)QA TeamQA TeamQA Team

Different Testing Stages and Terminologies for Product Team:

Different Testing Stages

Acronym

Definition

1Client / Member Firm TestingUATUser Acceptance Testing
2Application Level TestingBATBusiness Acceptance Testing
3Feature Level TestingFBATFeature BAT
4Block Level TestingBBATBlock BAT

Ai đang xem chủ đề này?
OceanSpiders 2.0
Di chuyển  
Bạn không thể tạo chủ đề mới trong diễn đàn này.
Bạn không thể trả lời chủ đề trong diễn đàn này.
Bạn không thể xóa bài của bạn trong diễn đàn này.
Bạn không thể sửa bài của bạn trong diễn đàn này.
Bạn không thể tạo bình chọn trong diễn đàn này.
Bạn không thể bỏ phiếu bình chọn trong diễn đàn này.

| Cung cấp bởi YAF.NET 2.2.4.14 | YAF.NET © 2003-2020, Yet Another Forum.NET
Thời gian xử lý trang này hết 0.704 giây.