[[BackLinksMenu]]

[[TicketQuery(summary=PROCESS_R4, 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 ==
Simplify process to reduce overhead. The aim of this revision is to modify the process to be less time consuming and as useful as possible.
== Task requirements ==
 * Analyse the current situation with the process
  * What is most time-consuming
  * What parts of the workflow are taking most time
  * What can be removed (substituted)
  * What should be introduced
 * Give your suggestions to the team for a discussion
 * Apply approved suggestions
== Task result ==
Process with less overhead
== Implementation idea ==
Process optimizations:
Process 
= Pre-workflow =
 * On weeklies stickies are chosen from the wall. Tickets are grouped according to what can be shown for one week.
= Analysis =
 * Part of the analysis is to give a good estimation of what exactly includes this group and what can be done for this amount of time. This is later approved on the review of the analysis.
 * Analysis must be reviewed before a design review is requested
 * Analysis review is done by non-programmers from the integrators team. Programmers may participate if needed.
= Design = 
 * Deadline for a design is Thursday (before progress check)
 * Reviews are requested by marking the ticket as "design finished", by skype or by using the CC field of the ticket. Marking the ticket as "design finished" is nessesary.
 * Design reviews are done by Integrators team.
  * For coding tasks by a programmer. Non programmers may participate if needed.
  * For non-coding tasks by a non-programmer.
= Implementation =
 * Implementation may start before a design review but a review must be requested first.
 * It is best to create more than one group and start group by group in order not to send all of your work at the end of the week.
 * Unofficial reviews during implementation or design are allowed.
 * Patches are uploaded as ticket attachment.
= Task specific =
 * Groups are created by the implementor or implementors of the tasks. Tickets are chosen depending on what will be done for one week.
 * Regular tasks are grouped in groups. These include Maintenance of internal backlog, repository, backup, blog, mail and forum. A deadline for these is defined (for example - end of minisprint 1)
= Other =
 * Internal backlog and reports are checked before the weekly. Reminders are send to people that missed filling them in.
 * Tasks that are with old statuses are considered new or implementation finished. If only an analysis is done, the task is considered as new.
 * Patches for design and implementation are attached in the corresponding wiki page.
== Related ==
^(Add links to related tasks that could be useful or helpful.)^

== How to demo ==
^(Provide instructions for demonstration of the task.)^

= Design =
^(Describe your design here.)^

= Implementation =
^(Describe and link the implementation results here (from the wiki or the repository).)^

= Testing =
^(Place the testing results here.)^

= Comments =
^(Write comments for this or later revisions here.)