Please enable JavaScript.
Coggle requires JavaScript to display documents.
Vaga AM - Coggle Diagram
Vaga AM
6) Como você lida com conflitos dentro da equipe ágil
Acknowledge the Conflict
Create a Safe Environment
Encourage Open Communication
Define the Problem
Private Discussions
Mediation
Focus on Interests, Not Positions
Collaborative Problem-Solving
Set Clear Expectations
Establish Team Norms
Follow Up
Learn and Improve
Continuous Improvement
Como você facilita reuniões do Scrum, como a Daily Standup?
Set the Right Tone
Keep it Time-Bound
Stand Up (face-to-face)
Follow the Three Questions
Rotate Speaking Order
Focus on the Team Board
Address Impediments Immediately
Encourage Active Listening
Keep it Solutions-Oriented
Avoid Detailed Problem Solving
Celebrate Achievements
Continuous Improvement
3) Como você lidaria com uma equipe que está resistente à adoção de práticas ágeis
Understand the Concerns
Communication and Education
Lead by Example
Involve the Team in Decision-Making
Address Specific Concerns
Provide Training and Support
Celebrate Successes
Create a Feedback Loop
Emphasize the Evolutionary Nature of Agile (Adapt)
Seek External Support
Você pode explicar o papel do Scrum Master em um projeto ágil
Facilitator of Scrum Events
Servant Leadership
Coaching and Mentoring
Shielding the Team
Continuous Improvement
Conflict Resolution
Removing Impediments
Monitoring and Metrics
Promoting Agile Principles
4) Quais são as principais diferenças entre o Scrum e o Kanban?
Framework vs. Methodology
Scrum: It is a framework with predefined roles (Scrum Master, Product Owner, and Development Team), events (Sprint Planning, Daily Stand-up, Sprint Review, Sprint Retrospective), and artifacts (Product Backlog, Sprint Backlog, and Increment).
Kanban: It is more of a methodology or a visual management system, with fewer predefined roles and events. Kanban focuses on visualizing work, limiting work in progress, and continuous delivery.
Roles and Responsibilities
Scrum: Defines specific roles
Kanban: Typically has fewer predefined roles. The roles are more flexible and can be adapted
Work Planning
Scrum: Work is planned in fixed-length iterations called Sprints
Kanban: Work is continuous, and there are no fixed iterations.
Time-Boxed vs. Continuous Delivery
Scrum: Emphasizes time-boxed iterations with a defined beginning and end (Sprints)
Kanban: Emphasizes continuous delivery with no predefined time-boxes
Change Management
Scrum: Changes to the scope or requirements are generally discouraged during a Sprint
Kanban: Embraces changes at any time.
Metrics and Optimization:
Scrum: Focuses on metrics like velocity and burndown charts to measure team performance. Estimatives accuracy
Kanban: Uses metrics like lead time and cycle time to measure the time it takes to complete work items
Visual Board
Scrum: Focus on Sprint
Kanban: focus on workflow
O que é metodologia ágil e por que ela é importante?
O que é:
project management and product development approach that prioritizes flexibility, collaboration, and customer satisfaction
It originated in the software development industry but has since been adopted across various sectors
emphasizes iterative progress, adaptive planning, and the quick delivery of small, functional components
Key principles of Agile include
Customer Involvement
Iterative Development
Collaborative Teams
Adaptive Planning
Continuous Feedback
Agile is important for several reasons
Flexibility
Customer Satisfaction
Efficiency (Adress problems early)
Collaboration
Quality