| | 1 | * SCRUM |
| | 2 | * iterative incremental process of software development |
| | 3 | * counts on one to take the initiative |
| | 4 | * roles |
| | 5 | * product owner - the voice of the customer |
| | 6 | * scrum master - solves problems |
| | 7 | * self-organizing team - does the progress |
| | 8 | * regular standup meetings to show progress, plan and solve problems |
| | 9 | * opening, closing and other meetings |
| | 10 | |
| | 11 | * Teams |
| | 12 | * Analysis - does the specification of features, keeps the product consistent |
| | 13 | * Functional - does the design and implementation of the platfoem and features |
| | 14 | * Release - does the final touch, delivers the final product |
| | 15 | |
| | 16 | * Workflow |
| | 17 | Tickets are the product backlog |
| | 18 | * New - part of the product backlog, hasn't been worked on |
| | 19 | * Analysis - what has to be done |
| | 20 | * Design - how it should be done |
| | 21 | * Implementation - actual implementation |
| | 22 | * Testing - problems, documentation |
| | 23 | Each of these has |
| | 24 | * Started - in progress, someone works on it |
| | 25 | * Finished - ready for a review |
| | 26 | * OK - reviewed and ready for the next phase (if any) |
| | 27 | |
| | 28 | * Discipline |
| | 29 | * workday starts 9:30 |
| | 30 | * work outside of office should be approved by the team leader |
| | 31 | * daily and monthly reports |
| | 32 | * internal backlog |
| | 33 | * meetings |
| | 34 | |
| | 35 | * Member requirements |
| | 36 | * Work towards the goal |
| | 37 | * Be honest |
| | 38 | * Take initiative |
| | 39 | * Look around |
| | 40 | * Seek improvements |
| | 41 | * Seek the most appropriate solution |
| | 42 | * Quality is not negotiable. Scope and resources are. |
| | 43 | * Accept the challenge |
