| | 33 | Suggestion for the simplified PROCESS page |
| | 34 | {{{ |
| | 35 | SCRUM |
| | 36 | * iterative incremental process of software development |
| | 37 | * counts on one to take the initiative |
| | 38 | * roles |
| | 39 | * product owner - the voice of the customer |
| | 40 | * scrum master - solves problems |
| | 41 | * self-organizing team - does the progress |
| | 42 | * regular standup meetings to show progress, plan and solve problems |
| | 43 | |
| | 44 | Teams |
| | 45 | * Analysis - does the specification of features, keeps the product consistent |
| | 46 | * Functional - does the design and implementation of the platfoem and features |
| | 47 | * Release - does the final touch, delivers the final product |
| | 48 | |
| | 49 | Workflow |
| | 50 | Tickets are the product backlog |
| | 51 | * New - part of the product backlog, hasn't been worked on |
| | 52 | * Analysis - what has to be done |
| | 53 | * Design - how it should be done |
| | 54 | * Implementation - actual implementation |
| | 55 | * Testing - problems, documentation |
| | 56 | Each of these has |
| | 57 | * Started - in progress, someone works on it |
| | 58 | * Finished - ready for a review |
| | 59 | * OK - reviewed and ready for the next phase (if any) |
| | 60 | |
| | 61 | Discipline |
| | 62 | * workday starts 9:30 |
| | 63 | * work outside of office should be approved by the team leader |
| | 64 | * daily and monthly reports |
| | 65 | * internal backlog |
| | 66 | * meetings |
| | 67 | |
| | 68 | Member requirements |
| | 69 | * Work towards the goal |
| | 70 | * Be honest |
| | 71 | * Take initiative |
| | 72 | * Look around |
| | 73 | * Seek improvements |
| | 74 | * Seek the most appropriate solution |
| | 75 | * Quality is not negotiable. Scope and resources are. |
| | 76 | * Accept the challenge |
| | 77 | }}} |
