wiki:PROCESS_R2
Last modified 16 years ago Last modified on 01/07/09 11:12:38

Error: Macro BackLinksMenu(None) failed
compressed data is corrupt

Error: Macro TicketQuery(summary=PROCESS_R2, 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

The PROCESS page should be tuned according to the new rules, expanding the team etc.

Task requirements

  • Create a new structure of the document - see implementation idea
  • Refactor roles
    • Explain remote implementors
  • Add a link to an internal process page where you should explain internal rules and other specific information. If possible add read permissions to internal team only
  • Explain teams (experimental)
  • Add nice graphic of the workflow
  • Collect rules for different teams and add them to the process page
    • Discuss rules with different teams.

Task result

PROCESS

Implementation idea

Tree structure of the PROCESS page:

PROCESS
|_TOC with links!
|_Overview
|_Scrum
|__Explanation
|__Tunes
|_Team roles
|_Teams
|_Workflow
|__Diagram
|__Explanation of States
|_Task Tips (Maybe these belong to PLATFORM_STANDARDS_GENERAL?!)
|_Rules
|__General
|__Discipline
|__Timeboxing

PROCESS_R0
PROCESS_R1

How to demo

Show the new PROCESS page to the team.

Design

  • Look at the SCS_ISSUE_TRACKER_SETUP_R1 and use the workflow diagram and the workflow steps from there. Correct the Task States section where needed.
  • Write down that we have remote implementors called free-lancers which take part in the teams(in Roles section).
  • For the team explanation use http://sophie2.org/trac/browser/manage/sched/teams-desc.odt and http://sophie2.org/trac/browser/manage/sched/teams.odg documents.
  • Edit the workflow adding team participation.(Analysis team does the analysis, Release team does the implementation reviews and testing phase)
  • Make a team-leader discussion which rules they use to lead their teams(if there are any particular).
  • There is no need for internal process page - we should write all in the PROCESS page.
  • There is no need for the Task Tips section as long as there is PLATFORM_STANDARDS_GENERAL document. See what can be useful from the PROCESS page and add it in the PLATFORM_STANDARDS_GENERAL(comments section for example).
  • There is no need of TOC with links because there is backlinks menu in the right.

Implementation

  • All steps of the design are completed except separation of the SCRUM section. I don't think we need explanation section so there are only one with explanation and tunes in it.
  • The useful thinks from Task Tips section is moved in the PLATFORM_STANDARDS_GENERAL page.

See PROCESS.

Testing

Comments

(Write comments for this or later revisions here.)