SA re defined part 3

From UG

(Difference between revisions)
Jump to: navigation, search
(Weekly Status update)
 
Line 15: Line 15:
Once a week everyone should update task status. Steps:
Once a week everyone should update task status. Steps:
-
* BA, SA, Developer, QA must update [[%Percent Complete mantis fields]]
+
* BA, SA, Developer, QA must update [[#Percent Complete mantis fields]]
* BA must post updated spreadsheets into [[:Category:Proj Plans]] and email to management
* BA must post updated spreadsheets into [[:Category:Proj Plans]] and email to management
* request meeting (if required) to resolve potential problems
* request meeting (if required) to resolve potential problems

Current revision as of 17:43, 23 December 2010


Contents

[edit] Intro

This is a 3rd part of the article. Previous: SA re defined part 2

[edit] Monthly BA and SA planning process

I introduce monthly plans for BAs and SAs.

See examples under Category:Proj Plans

[edit] Weekly Status update

Once a week everyone should update task status. Steps:

[edit] Percent Complete mantis fields

These fields indicate estimated % of task completed. Examples: 5% - just started; 100% - fully completed

Should be updated once a week before #Weekly Status update meetings.

%BA - to be set by BA
%SA - to be set by SA
%Dev - to be set by Developer
%QA - to be set by QA engineer
%UAT - to be set by BA
%WU - to be set by BA
Personal tools