is a philosophy of IT project management. • It is designed to be customer-driven with flexibility and fast delivery. • It has a constant feedback loop with iteration.
is a lightweight project management framework that is the most popular implementation of Agile development in the software industry. • It consists of three theories, five values, artifacts, roles, and events to manage the software project effectively and efficiently.
is transparent through the artifacts and events. Features, progress, and communication must be transparent to all who get involved in the project. • Transparency increases the value of the product because it leads to valuable discussion. • Transparency enables inspection. Inspection cannot be done without transparency.
constantly checks and shares the progress and goal to detect the potential risks. • Inspection is conducted through the five Scrum events: Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective. • Inspection enables adaptation. As a result of the inspection, the Scrum Team can adapt to change.
is adaptable to be flexible and prevent deviation as a result of the inspection. • Adaptation is one of the critical characteristics of the Scrum Team in order to meet the changeable market and customer requests. • Adaptation prevents the common mistake that the software development team creates unwanted products after spending a long time developing.
Scrum Team focuses on the Sprint Goal to complete delivery. Openness : The Scrum Team is open to communicating, sharing, and helping. Courage : The Scrum Team challenges the status quo to innovate. Commitment : The Scrum Team is committed to the team. Respect : The Scrum Team respect each other.
is the most important artifact in Scrum because it describes everything of the product: functions, requirements, enhancements, bug fixes, etc, and prioritizes them. • Is associated with one product. Even though multiple teams work for a single product, the Product Backlog must be one. • Exists and evolves as long as the product exists and evolves.
is the set of Product Backlog Items selected to achieve for the upcoming Sprint. • The Development Team estimates to select based on the priority of the Product Backlog and realistic forecast. • Sprint Backlog is updated throughout the Sprint as the development progress.
sum of all the Product Backlog items completed in all previous Sprints. • is created when the Product Backlog item meets the definition of done that is the common understanding of completion in the project. • is releasable whenever the Product Owner wants to release.
Owner: • is responsible for maximizing the value of the product by clarifying, managing, and prioritizing the Product Backlog. • ensures the Product Backlog is visible, transparent, and clear to all. • is a one person, not a committee.
Master: • plays a key role in the team to establish the Scrum. • removes impediments in the team so that the Scrum Team can work smoothly and effectively. • facilitates the Scrum Events to be positive, productive, and time-boxed.
for creating increments throughout the Sprint. • Plan for the Sprint by selecting the Sprint Backlog. • Ensure the quality of the product by having a professional skills and adhering to Definition of Done.
a fixed-length event that the Scrum Team works to make Increments. • All Scrum Events: Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective are held during the Sprint. • must be less than a month, and the shorter the Sprint, the better because the Scrum Team can generate more learning cycles.
the Sprint Planning, The Scrum Team plans which Product Backlog items they work on to complete at the end of the Sprint. • The Scrum Team discusses to decide which Product Backlog items meet the Product Vision and increase the product's value. • The Sprint Planning is time-boxed, and The Scrum Team needs to discuss three questions: why is this Sprint valuable, what can be done this Sprint, how will the chosen work get done.
the Daily Scrum, the Scrum Team inspects the progress and impediment. • Daily Scrum is held every day and 15-minutes timeboxed. • Developers answer those three questions. What I did yesterday. What I will do today. What impediments hold me back.
of the Sprint Review is to inspect the outcome that the Scrum Team accomplished during the Sprint and discuss what they will do for the next Sprint based on the outcome and changes of the environment. • The Scrum Team demonstrates the outcome to key stakeholders during the Sprint Review. • Sprint Review is timeboxed to a maximum of four hours for one- month Sprint. If the Sprint is less than a month, Sprint Review is also shorter.
of the Sprint Retrospective is to share and discuss what they can do better for future improvement based on the current Sprint. • The topics can be anything as long as they improve to achieve better values such as process, tools, technologies, communication, etc. • As the result of the Sprint Retrospective, the Scrum Team picks up the most helpful changes to create the Product Backlog to implement in the next Sprint.
Education and communication 2. Participation and involvement 3. Facilitation and support 4. Negotiation and agreement 5. Manipulation and co-optation 6. Explicit and implicit coercion Source: Choosing Strategies for Change
eiki
subroh0508
o11yfes2023
miura55
gachimuchiengineer
hikarut
yudai00
nishiuma
yasumuusan
sansan_randd
yoyoyopg
taisukearase
ma2shita
garrettdimon
chriscoyier
jeffersonlam
zenorocha
eileencodes
philhawksworth
paigeccino
addyosmani
sonatard
eitanlees
lauravandoore
morganepeng
