realizată de Gemma Muray 8 ani în urmă
297
Mai multe ca aceasta
Welcome!
This Smart Map helps you to outline the plan for an Agile project. The wizard shows you the basic principles, so that you can then leave the wizard behind and continue to develop the map as a regular Mindomo map.
The purpose of using a Mindomo map is to create a focus for discussion and explanation, which is an important principle of Agile. You can use the map to discuss and explain stories, specifications, features and plans. The map aims to capture an accurate description of the work to be done, but does not manage the project around it.
Add your project name
Begin by typing in the name of your project, then press Enter.
Stories
Stories are the heart of an Agile plan. They describe something that can be tested, delivered and actually used by Users.
When adequately defined, Stories can be moved to belong to a Sprint below. A Sprint is a group of Stories that build a working part of a solution.
Just add a couple of user stories here to establish the idea. You can add more later.
Add a user story
Type in a user story, in the following format:
'As a [A], I need to [B], so that I can [C]'
where:
[A] is a user role,
[B] is what the user needs to do, and
[C] is why they need to do it.
Example: 'As a registered user, I need to be able to change my password, so that I can manage security'.
Click on an icon to rank the importance of this Story:
Add a feature, function or task
What features, functions or tasks will be needed to deliver this story in a working form? What components must be working? What needs to be researched and designed?
Add an item and press Enter. Just add a few to get the idea - you can add more later when editing the map as a Mindomo map.
How complex is this story?
Estimate the relative complexity of this story, expressed as story points. Trivial things are only a point or two, and average is about 5 points. If you find it hard to guess, you may need to break it down further into smaller stories.
Make your selection and press Enter.
Define your users
Next, we will make a list of Users. These are the people who will interact with the solution that you are creating. They will have reasons for wanting to use the solution, and expectations of what it should and should not do. Users are identified not by personal name, but by their role in relation to the task they perform.
For the purposes of this wizard, just enter a couple of user roles to establish the idea. You can add more later.
Add a User role
Type in a User role and press Enter. Typical roles for an IT solution might be:
Epics
Epics are the major stages in a project, and are divided up into sprints.
An epic is often a product release point or a handover to the customer.
You will probably already have a good idea of the major milestones in your project. You do not need to fully plan them here and now, as you can modify them later on.
Add an Epic
Add an Epic (major project phase) to the map. If you have a target date in mind, include it in the topic text for clarity.
Summarise your project
We will begin with a summary of the key points of your project, to act as a reference for discussions.
Add a key point about your project
Add a key point about your project. Consider:
