SCRUM!!!!
-
The Scrum process
The Scrum process encourages practitioners to work with what they have and continually evaluate what is working and what is not working. Communication, which is an important part of the process, is carried out through meetings, called Events. Scrum Events include:
Daily Scrum . The Daily Scrum is a short stand-up meeting that happens at the same place and time each day. At each meeting, the team reviews work that was completed the previous day and plans what work will be done in the next 24 hours. This is the time for team members to speak up about any problems that might prevent project completion.
Sprint Planning Meeting. A Sprint refers to the time frame in which work must be completed, and it's often 30 days. Everyone participates in setting the goals, and at the end, at least one increment -- a usable piece of software -- should be produced.
Sprint Review. This is the time to show off the increment.
Sprint Retrospective. A Sprint Retrospective is a meeting that's held after a Sprint ends. During this meeting, everyone reflects on the Sprint process. A team-building exercise may also be offered. An important goal of a Sprint Retrospective is continuous improvement.
Product backlog. This refers to what remains on the "to be done" list. During a product backlog grooming session, the development team works with the business owner to prioritize work that has been backlogged. The product backlog may be fine-tuned during a process called backlog refinement.
Sprint backlog. This is a list of tasks that must be completed before selected product backlog items can be delivered. These are divided in to time-based user stories.
Product increment. This refers to what's been accomplished during a Sprint -- all the product backlog items -- as well as what's been created during all previous Sprints. The product increment reflects how much progress has been made.
Burn-down. The burn-down is a visual representation of the amount of work that still needs to be completed. A burn-down chart has a Y axis (work) and an X axis (time). Ideally, the chart illustrates a downward trend, as the amount of work still left to do over time burns down to zero.
Scrum is a framework for project management that emphasizes teamwork, accountability and iterative progress toward a well-defined goal. The framework begins with a simple premise: Start with what can be seen or known. After that, track the progress and tweak as necessary. The three pillars of Scrum are transparency, inspection and adaptation.
Scrum salamander:
-
Backlogs : Product backlog aims to determine the priority of what should be done during the sprint workmanship, namely meeting the manufacture of software that is done in accordance with the agreed duration. Product backlog involves all related teams.
-
Wip: In this process, the whole team gathered to formulate what tasks you want to work on and release in the future. each team member shares what has been done, and what will be done on that day. Team members can also report on obstacles encountered during the work.
-
In QA + review: it's time for team members to demonstrate what's done in a sprint. Sprint review is done after one sprint finish.
-
Done: project finish by tech”s team and project live
Scrum values
-
Commitment: The team is self-directed, and all members are dedicated to completing work that has been agreed upon.
-
Courage: The team operates as a single entity and succeeds or fails together.
-
Focus: The team limits distractions and concentrates on what work needs to be done today.
-
Openness: The team is given time to gather and share what has been successful and what needs to be improved.
-
Respect: The team is composed of members who have different strengths, and each individual's strengths are respected. There is no finger-pointing when discussing how to fix what is not working.
