Error: Macro BackLinksMenu(None) failed

compressed data is corrupt

Error: Macro TicketQuery(summary=UNPLANNED_PLATFORM_STANDARDS_GENERAL_R0, format=table, col=summary|owner|status|type|component|priority|effort|importance, rows=description|analysis_owners|analysis_reviewers|analysis_score|design_owners|design_reviewers|design_score|implementation_owners|implementation_reviewers|implementation_score|test_owners|test_reviewers|test_score|) failed

current transaction is aborted, commands ignored until end of transaction block

Analysis

Overview

Rules for reviewing Analysis, Design, Implementation and Testing are needed. This task is because there are no tasks for platform standards analysis and general in this iteration.

Task requirements

For PLATFORM_STANDARDS_ANALYSIS

• Split each task type into sections
  • Required - things that are obligatory for the analysis in order to pass the review.
  • Recommended - things that are recommended for the analysis, needed for higher score
  • Optional - things the analysis owner assumed useful, may be rated with the higher score.
• Discuss which of the comments in PLATFORM_STANDARDS_ANALYSIS should be included in the documents as rules
• Add a requirement that the reviewer should either stick to these rules or comment them in the comment section.
• Explain when requesting a superreview is allowed.

For PLATFORM_STANDARDS_GENERAL

• Split each task type into sections (excluding code and bug fix tasks - they are explained in PLATFORM_STANDARDS_CODE
  • Required - things that are obligatory for the implementation in order to pass the review.
  • Recommended - things that are recommended for the implementation, needed for higher score
  • Optional - things the implementation owner assumed useful, may be rated with the higher score.
• Discuss which of the comments in PLATFORM_STANDARDS_GENERAL should be included in the documents as rules
• Add a requirement that the reviewer should either stick to these rules or comment them in the comment section.

Task result

Refactored PLATFORM_STANDARDS_ANALYSIS and PLATFORM_STANDARDS_GENERAL with exact review requirements.

Implementation idea

Change the formatting of the documents with

=== Task type ===

instead of

 * Task type

Related

PLATFORM_STANDARDS_ANALYSIS
PLATFORM_STANDARDS_GENERAL

How to demo

Show refactored PLATFORM_STANDARDS_ANALYSIS and PLATFORM_STANDARDS_GENERAL

Design

For PLATFORM_STANDARDS_ANALYSIS

The PLATFORM_STANDARDS_ANALYSIS page will have the following structure:

|_How to write analyses
|__General information
|__Task types
|___Coding task
|___Bug fix
|___Document
|___Setup
|___Maintenance
|__Examples
|__Coding tasks approach
|__Reviewing
|___Scores
|___Super review
|_Comments

These sections will contain:

• General information - a brief description of the structure of the analysis and what each of its sections should contain (applying to all task kinds).
• Task types - for each task type there will be a list of what each section of the analysis should contain (split into required, recommended, optional).
• Examples - several examples of good and bad analyses with brief explanations of their pro and cons.
• Coding tasks approach - a list of things to have a look at when analyzing coding tasks (for example, the WBS file, the task index, etc.).
• Reviewing - rules for reviewing, scoring and requesting a super review - when a task should fail and when not.
• Comments - everyone that has some opinion on the standards should describe it here.

Everyone has been asked to give his opinion in the Comments section. During the implementation these comments will be considered and integrated into the wiki page.

Implementation

^{(Implementation results should be described and linked here (from the wiki or the repository))}

Testing

Comments

^{(Write comments for this or later revisions here.)}