[[BackLinksMenu]]

[[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|)]]
= Analysis =
== Overview ==
The tasks for imroving the process define rules that ease the work process.
== Task requirements ==
 * Throughly review [wiki: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
  * [wiki:PROCESS/Analysis]
  * [wiki:PROCESS/Functional]
  * [wiki:PROCESS/Release]
 * Discuss with team leaders of the functional teams the differences between their processes - you may decide [wiki:PROCESS/Functional] more adequate than Base Main Server.
 * Explain meetings further
  * Interteam meetings
  * Weekly
  * Progress checks
  * Sprint opening
  * Sprint closing [[BR]]
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 [wiki: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 [wiki:PROCESS] page so it looks exactly like now.
== Task result ==
Improved [wiki: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:
[wiki:PROCESS/Overview] [[BR]]
[wiki:PROCESS/SCRUM] [[BR]]
[wiki:PROCESS/InternalBacklog] [[BR]]
[wiki:PROCESS/Teams] [[BR]]
[wiki:PROCESS/Workflow] [[BR]]
[wiki:PROCESS/Rules] [[BR]]
[wiki:PROCESS/Discipline] [[BR]]


== Related ==
[wiki:PROCESS_R2][[BR]]
[wiki:PROCESS_R1][[BR]]
[wiki:PROCESS_R0][[BR]]
== How to demo ==
Show Process page and subpages. Explain improvements.

= Design =

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