Certified SCRUM Master (CSM)
Certified SCRUM Master (CSM)
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer Collaboration over Contract negotiation
Responding to change over following a plan
Agile Principles
Our highest priority is to satisfy the customer through early and continous delivery of valuable software
Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.
Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
Business people and developers must work together daily throughout the project
Build projects around motivated individuals. Give them the environment and support they need and trust them to get the job done.
the most efficient and effective method of conveying information to and within the Development team is face-to-face conversation.
Working software is the primary measure of progress.
Agile processes promote sustainable development. The sponsors, developers and users should be able to maintain a constant pace indefinitely.
Continuous attention to technical excellence and good design enhances agility.
Simplicity - the art of maximizing the amount of work done (avoiding non-value adding work) - is essential.
The best architectures, requirements and designs emerge from self-organizing teams.
At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behaviour accordingly.
SCRUM is an Agile Project Management Framework that teams use to develop, deliver and sustain complex products. SCRUM is about continuously shipping value to customers. Its a framework for getting work done while Agile is a set of values and principles.
We can use a framework like SCRUM to start thinking in a more Agile way and practice building more Agile ways into our communication and our work. All kinds of teams use SCRUM (HR, marketing, design, software development and engineering. Software is a living, breathing thing. Requirements change, goals change, situations change. SCRUM embraces these changes.
With SCRUM, a product is build in a series of iterations called Sprints that breakdown big complex projects into manageable pieces. This allows teams to ship more high quality work faster and gives them more flexibility to adapt and change.
In a nutshell, SCRUM requires a SCRUM Master to foster an environment where:
A product owner orders the work for a complex problem into a Product Backlog.
The SCRUM Team turns a selection of the work into an Increment of value during a Sprint.
The SCRUM Team and its stakeholders inspect the results and adjust for the next Sprint.
Repeat