Products Solutions Samples Buy
✕
Made with
ConceptDraw
MINDMAP 16
Download ConceptDraw Trial

Sprint Retrospective

Project Management

In PM solutions we support many project methodologies such as Agile and Simple Projects. Methodology solutions help in implementing best practices in project management. CS Odessa provides Toolbox solutions to support solving issues related to planning, tracking, milestones, events, resource usage, and other typical project management functions. Toolbox Solutions help you deal with common project situations in an extraordinary way.

PM Agile

Benefits

All Agile meetings and documents are powered by mission adapted mind map templates, specially tuned for collaborative work. Tracking project Velocity is easy when using ConceptDraw Velocity diagram templates.

Objective

Support Agile methods such as user stories, iteration planning, burndown charts, backlogs, and velocity.

Solution Purpose

These visual tools assist in the holding of Scrum-meetings, collaborative planning for Sprint, maintaining backlog, and calculating and reporting the Velocity of the team.

Intended For

Companies using Agile methodology; specifically, Scrum; Product Owners, Scrum Masters.

Products and methods

In the background of this solution we use mind mapping for visualization of key events and artifacts of Agile methodology. Key diagrams for visualization are made by ConceptDraw DIAGRAM

Use Sprint Retrospective to visualize the Sprint Retrospective meeting agenda as a mind map.

Sprint Retrospective *

Example 1. Sprint Retrospective


Export to Outline


Sprint Retrospective Meeting Agenda
    • Rules
      • The Retrospective is held after the Sprint Review (Demo) meeting, before the next Sprint Planning meeting.
      • All team members answer two questions:
        • What went well during the Sprint?
        • What could be improved in the next Sprint?
      • The scrum master record the team’s answers.
      • The team set the improvements order to discuss.
      • The improvement actions for the next Sprint should be added to the Product Backlog as non functional issues with high priority.
      • Time box: 45 min per week of the Sprint.
    • Appointment
      • Date: ___ __, 201_
      • Start Time: __ : __
        • End Time: __ : __
      • Venue: ____________________
      • Project: __________________________
      • Release: _____
      • Sprint # ___
      • Attendees
        • Required
          • Scrum Master (Facilitator):
            • ______________________
          • Team Members:
            • ______________________
            • ______________________
            • ______________________
            • ______________________
            • ______________________
            • ______________________
            • ______________________
            • ______________________
            • ______________________
        • Optional
          • Product Owner:
            • ______________________
    • Team answers to the questions
      • Name: __________________________
        • What went well during the Sprint?
          • Answer
        • What could be improved in the next Sprint?
          • Answer
      • Name: __________________________
        • What went well during the Sprint?
          • Answer
        • What could be improved in the next Sprint?
          • Answer
      • Name: __________________________
        • What went well during the Sprint?
          • Answer
        • What could be improved in the next Sprint?
          • Answer
      • Name: __________________________
        • What went well during the Sprint?
          • Answer
        • What could be improved in the next Sprint?
          • Answer
      • Name: __________________________
        • What went well during the Sprint?
          • Answer
        • What could be improved in the next Sprint?
          • Answer
      • Name: __________________________
        • What went well during the Sprint?
          • Answer
        • What could be improved in the next Sprint?
          • Answer
      • Name: __________________________
        • What went well during the Sprint?
          • Answer
        • What could be improved in the next Sprint?
          • Answer
      • Name: __________________________
        • What went well during the Sprint?
          • Answer
        • What could be improved in the next Sprint?
          • Answer
      • Name: __________________________
        • What went well during the Sprint?
          • Answer
        • What could be improved in the next Sprint?
          • Answer
      • Name: __________________________
        • What went well during the Sprint?
          • Answer
        • What could be improved in the next Sprint?
          • Answer
    • Discussion of the improvements
      • Improvement: _____________________
        • Action: __________________________
      • Improvement: _____________________
        • Action: __________________________
      • Improvement: _____________________
        • Action: __________________________

The Benefits for ConceptDraw MINDMAP Brainstorming Software

  • ConceptDraw MINDMAP is effective for brainstorming, designing mind maps, idea generating, creative and lateral thinking, creativity and problem solving.
  • ConceptDraw MINDMAP is ideal for team and personal work in Business, Marketing and Project Management.
  • The libraries with large quantity of vector objects help to illustrate your mind maps and to make them bright, visual and comprehensible.
  • Use of View Navigator tool lets create presentations from a mind map: you can simply select the map parts you want to present, sequence your slides, and preview the presentation.
  • ConceptDraw MINDMAP provides wide capabilities of importing and exporting in various formats: Microsoft PowerPoint, Microsoft Word, MS Excel, Mindjet MindManager, image, HTML, PDF file.





THREE RELATED HOW TO's:
Sprint Backlog →
Use Sprint Backlog to visualize the Sprint Backlog.Sprint Backlog *
Picture: Sprint Backlog
Related Solution:
Mind Map Exchange
Data Flow Diagrams →
Software development flourishes nowadays. Students have tons of educational information and courses that would fit every taste. And it's no secret that knowing how to draw data flow diagrams is a useful skill for a future software architect. The diagrams help a lot in understanding how to storage data effectively and how data processes within a system. This data flow diagram represents the model of small traditional production enterprise. It was created using Yourdon and Coad notation. The data flow diagram include four main objects: entity, process, data store and data flow. Yourdon and Coad notation uses circles to depict processes and parallel lines to represent data stores. Dataflows are shown as arrowed lines. They are labeled with the description of the data that move through them. Dataflow's role is to deliver the pieces of information. A process's function is to transform. the input data flow into output data flow. ConceptDraw Data Flow Diagrams solution contains the data flow diagram symbols of both Yourdon-Coad and Gane-Sarson notations and a set of handy templates to get started with DFD.Data Flow Diagrams *
Picture: Data Flow Diagrams
Related Solution:
Data Flow Diagrams (DFD)
MS Word →
PM Meeting makes preparing for meetings a quick task. Meetings become more efficient because of the ability to easily record results. Collaborative decisions made by the project team are captured as part of the meeting process and then distributed. This innovative process makes meetings more productive and keeps activities on track. Meeting notes can be easily distributed at a meeting's conclusion to all participants and stakeholders.MS Word *
Picture: MS Word
Related Solution:
Mind Map Exchange
ConceptDraw
MINDMAP 16
Buy it Now