wiki:PROCESS_R3

Version 12 (modified by deyan, 16 years ago) (diff)

--

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

Error: Macro TicketQuery(summary=PROCESS_R3, 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 tasks for imroving the process define rules that ease the work process.

Task requirements

  • Throughly review PROCESS
    • See comments section for some improvement ideas
  • Create a list of documents similar to important docs that contains only the documents that every team member MUST read.
  • Create sub-pages for the processes of different teams
  • Discuss with team leaders of the functional teams the differences between their processes - you may decide PROCESS/Functional? more adequate than Base Main Server.
  • Explain meetings further
    • Interteam meetings
    • Weekly
    • Progress checks
    • Sprint opening
    • Sprint closing

What is done on these meetings, what should one prepare. Exact times are not important - just which meetings are regular and periods.

  • A new requirement is to simplify the PROCESS.
    • Create subpages of existing PROCESS which contain the information from the current sections of the document.
    • Create a simple process page which contains only plan with links to the explanations
    • Include all of the process subpages into the PROCESS page so it looks exactly like now.

Task result

Improved PROCESS page. Subpages of the process page linked in it. A simplified version of the current page.

Implementation idea

  • Pair with the team leaders or team members for sub-team team process pages.

Suggestion for the simplified PROCESS page 

SCRUM
 * iterative incremental process of software development
 * counts on one to take the initiative
 * roles
  * product owner - the voice of the customer
  * scrum master - solves problems
  * self-organizing team - does the progress
 * regular standup meetings to show progress, plan and solve problems
 * opening, closing and other meetings

Teams
 * Analysis - does the specification of features, keeps the product consistent
 * Functional - does the design and implementation of the platfoem and features
 * Release - does the final touch, delivers the final product
 
Workflow
Tickets are the product backlog
 * New - part of the product backlog, hasn't been worked on
 * Analysis - what has to be done
 * Design - how it should be done
 * Implementation - actual implementation
 * Testing - problems, documentation
Each of these has
 * Started - in progress, someone works on it
 * Finished - ready for a review
 * OK - reviewed and ready for the next phase (if any)
 
Discipline
 * workday starts 9:30
 * work outside of office should be approved by the team leader
 * daily and monthly reports
 * internal backlog
 * meetings
 
Member requirements
 * Work towards the goal
 * Be honest
 * Take initiative
 * Look around
 * Seek improvements
 * Seek the most appropriate solution
 * Quality is not negotiable. Scope and resources are.
 * Accept the challenge

Process subpages: PROCESS/Overview
PROCESS/SCRUM?
PROCESS/InternalBacklog
PROCESS/Teams
PROCESS/Workflow
PROCESS/Rules
PROCESS/Discipline

PROCESS_R2
PROCESS_R1
PROCESS_R0

How to demo

Show Process page and subpages. Explain improvements.

Design

PROCESS/Simple

  • For sections will be used bold instead of headings
    • The aim is to make the document as compact as possible
    • Links will be more visible
  • The PROCESS will be done by including the subpages with "Edit" link for each section for more convinent editing.
  • Following should be updated:
    • Workflow - groups (group tickets) will be added
    • Teams - analysis, functional and release
  • Rules section will be renamed to MemberRequirements
  • Inconsistent formatting will be removed
  • Overview page 
    In order to produce the highest quality product (both internal and external), we have defined process guidelines in this section. (This is related to the SCRUM mandatory definition of the done status state.)

This will help us meet the following challenges:

    * Internal quality (quality of code)
    * External quality (quality of the visible product)
    * Documentation reading (many things are written, few things are read)
    * Reducing unuseful process overhead
  • Scrum page 
    We are continuing to use SCRUM methodology (info at http://en.wikipedia.org/wiki/SCRUM). What is new:

    * Trying to have much higher quality.
    * The sprint backlogs are on wiki pages ([wiki:ITERATION_01] for example).
    * The [wiki:PROCESS/Meetings Meetings] are: 
		* weekly meetings
		* progress checks
    * Using a customized and flexible [wiki:PROCESS/Workflow]

We have an internal backlog which should track:

    * Impediments backlog
    * Documentation backlog
    * Smells
    * Open Questions 

Here is the document: Backlog

The internal backlog structure may be found and linked in this document instead of bullet listing it.

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.)