Agile Development
2024-08-29 13:59:00 193 1 Report 0
0
Login to view full content
This mind map serves as a comprehensive overview of Agile Development, specifically focusing on the Scrum Framework. It outlines the core principles of the Agile Manifesto, emphasizing the importance of individuals, working software, customer collaboration, and adaptability to change. The framework is structured around three key roles: the Product Owner, Scrum Master, and Development Team, each with distinct responsibilities. It details essential workpieces like the Product Backlog and Sprint Backlog, and highlights four critical events: sprint planning, daily stand-ups, sprint reviews, and retrospectives. The mind map also underscores five core values integral to Scrum: commitment, focus, openness, respect, and courage.
Other creations by the author
Outline/Content
Agile Manifesto
Individuals and interactions are more important than processes and tools.
Working software is superior to comprehensive documentation.
Customer cooperation is above contract negotiation.
Responding to change is more important than following a plan.
3 characters
Product Owner - Product Owner
Abbreviation:
PO
Personnel:
The role is typically held by a product manager/product director.
Duties:
is the sole person responsible for the product backlog
Maximize the value of the products developed by the team
Break down the stories in the product backlog into user stories for the Sprint.
Ready to answer any questions the team may have about user stories
Scrum Master - Agile Coach
Abbreviation:
SM
Personnel:
is played by a professional Agile coach
However, most of these roles are filled by individuals from reputable companies who are knowledgeable about Agile development.
Duties:
Help the team understand the theory and practice of Scrum
Ensure that events in Scrum are completed on time
Help the team remove obstacles in the work progress
Help the team create high-value products
Team - Development Team
Abbreviation:
team
Personnel:
Composed of various cross-functional personnel: front-end, back-end, testing, architecture, and so on...
Responsibilities:
Everyone is equal, without distinction of titles, all are part of the team.
Transform the requirements in the product backlog into deliverable product increments.
3 workpieces
Product Backlog
The list is fully managed by PO.
This list item has these attributes: description, order, estimate, and value.
The product backlog is dynamic and requires continuous updates to reflect what the product needs to maintain its relevance and competitiveness.
Sprint backlog
The list is fully managed by the team.
The Sprint backlog consists of the highest priority user stories selected from the product backlog.
The Sprint backlog is highly visible and reflects the team's progress on work completed within the current Sprint in real-time.
Product volume increase
The increment is the sum of all product backlog items completed during a Sprint.
as well as the total value of all increments produced by previous Sprints
The increment must be available regardless of whether the product owner decides to release it or not.
4 events
sprint planning will
Time:
Sprint Day One execution
The duration of the meeting depends on the iteration cycle.
The period is generally no more than 4 hours for a 2-week cycle; for a 4-week cycle, it is generally no more than 8 hours.
Personnel:
PO
SM
All team members
Event:
The PO explains to the development team the content that needs to be completed in the current Sprint (explaining user stories).
After the PO explains the iteration content, team members work together to break down the tasks (into specific tasks from the story).
Every day stand-up meeting
Time:
Sprint cycle requires daily execution (generally recommended in the morning).
The recommended duration for a meeting is generally no more than 15 minutes.
Personnel:
PO (Optional Participation)
SM
All team members
Event:
Each team member speaks in turn.
The content of the speech consists of three sentences.
I did what yesterday...
What difficulties have I encountered, what kind of help do I need...
What am I planning to do today...
After the speech, pick up the task on site (i.e., commit to the tasks that need to be completed today).
sprint review meeting
Time:
Sprint final day execution
The duration of the meeting depends on the iteration cycle.
The cycle, which is two weeks, generally does not exceed two hours; the cycle, which is four weeks, generally does not exceed four hours.
Personnel:
PO
SM
All team members
Stakeholders' requirements
Event:
The team demonstrates the completed features to the stakeholders during the Sprint.
The team addresses functional issues of stakeholders.
sprint retrospective meeting
Time:
It is recommended to perform on the last day of the Sprint.
The duration of the meeting depends on the iteration cycle.
The review meeting generally does not exceed 3 hours.
Personnel:
PO
SM
The entire team
Invite/decline the leader to attend the meeting as appropriate
Event:
The team members review the issues encountered during the current Sprint.
Discuss solutions for the aforementioned issues to facilitate improvement in the next Sprint.
Inspect the improvement of issues from the last Sprint.
Note: This meeting is informal, and team members are free to speak up (they can even buy some snacks to reward the team).
5 values
Commitment: willing to make a commitment to the goal
Focus: Apply your thoughts and abilities entirely to the work you have committed to.
Open: Scrum opens everything in the project for everyone to see.
Respect: Everyone has their unique background and experience.
Courage: Having the courage to make commitments, keep promises, and accept others' respect.
Collect
Collect
0 Comments
Next page
Recommended for you
More
