Please enable JavaScript.
Coggle requires JavaScript to display documents.
Agile Project Management (Characteristics (Empowered Team (Each member…
Agile Project Management
-
-
-
adaptive, distributed process with just enough and continuous planning.
-
Scrum
-
-
Founded on empirical process control theory, or empiricism
Transparency,
inspection, and adaptation.
Framework for developing, delivering, and sustaining complex projects.
-
-
Each increment contains the result of the previous iterations. increment is the complete state of the product after an iteration
-
-
-
-
-
-
-
Framework to address complex adaptive problems, by ensuring productively and creatively delivering products of the highest possible value
Lightweight, Simple to understand and difficult to master
Not a process, technique or a definitive method
-
Rules of Scrum bind together the roles, events, and artifacts, governing the relationships and
interaction between them
Continuously improve the product, the team, and the working environment.
Consists of Scrum Teams and their associated roles, events, artifacts, and
rules
Atlassian JIRA
-
Boards
-
Kanban Board, Scrum Board, Task Board etc.
-
-
-
A single project can have multiple boards and
a single board can contain the issues of multiple projects.
-
-
-
-
-
Workflows
-
Series of steps, processes
-
-
-
-
-
Scrum Artifacts
-
-
Product backlog
-
-
-
-
include issues that represent features, improvements, bug fixes or any other type of issue
-
-
Artifacts : Scrum artifacts provide project transparency, enable shared understanding, and enable inspection and adaptation both inside and outside of scrum meetings.
-
Scrum Events
Sprint Planning
-
Team usually discusses the sprint goal, modifies the sprint backlog, places story point estimates on issues, and adds details to the issues to better describe the specific work to be done.
-
-
-
-
-
-
-
-
Configuring scrum artifacts, and monitoring sprint progress
Sprint Retrospective
-
Team to inspect itself including its processes, tools, and team interaction
-
-
Team usually discusses what they should keep doing, what they should stop doing, and what they should start doing
-
-
Sprint Review
-
-
-
Purpose of the meeting is to inspect the increment that was just created in the sprint and to collaboratively update the product backlog.
Meeting with a lot of feedback on the project and includes a brainstorming session to help decide what to do next
-
Daily Standups
-
purpose of the meeting is to inspect recent progress toward the sprint goal, plan the day's work, and identify any impediments to the team
-
-
-
A sprint contains four formal events for inspection and adaptation. You may also hear events referred to as ceremonies or simply meetings. Scrum events occur at regular intervals and minimize the need for other meetings. These events are designed to maximize the opportunities for feedback, and continuous learning, and are a key part of achieving agility.
Meetings can never go over their allotted time, but they can be ended early if the purpose of the meeting is achieved.
Primarily to plan, inspect, and adapt. In agile projects, the planning is distributed throughout the project rather than the mostly upfront planning of waterfall projects.
Scrum Roles
Scrum Master
-
-
-
-
-
-
-
-
-
-
Configuring scrum artifacts, and monitoring sprint progress
-
-
Cross-functional self organizing team members for completing the stories within the team. The team is responsible for deciding how to organize and do its work. Stakeholders are not members of the scrum team, but are interested in the success of the project.
-
-
-
