|This article may meet Wikipedia's criteria for speedy deletion for the following reasons:|
If this article does not meet the criteria for speedy deletion, or you intend to fix it, please remove this notice, but do not remove this notice from pages that you have created yourself. If you created this page and you disagree with the given reason for deletion, you can click the button below and leave a message explaining why you believe it should not be deleted. You can also visit the talk page to check if you have received a response to your message.
Note that once tagged with this notice, this article may be deleted at any time if it unquestionably meets the speedy deletion criteria, or if an explanation posted to the talk page is found to be insufficient.
Administrators: check links, history (last), and logs before deletion. Consider checking Google.
This page was last edited by HemovanadinCSDbot at 04:11 UTC (10 months ago)
Projectmap "Project Map" redirects here.
A Projectmap showing three Categories of activity and three planning objects: activity, buffer and milestones. A Projectmap is a type of block diagram, devised by Yaniv Shor in 2016, that illustrates a project plan. Projectmap illustrates the overall structure of the project plan, the main areas of activity (teams and workstreams), the activity chain(s) within each area and the links between them. Milestones are used to show cross category delivery targets and intermediate targets. Projectmap can be used to show a project plan during the planning phase before the start date, or the project status during the project’s execution. Color codes and icons are used to show progress, delays and percent-complete shadings against a vertical "TODAY" line. Although regarded as a common block diagram technique, the methodology behind Projectmap is revolutionary in the way intuitive planning, using simple shapes and connectors can be captured in a data structure enabling automatic metrics extraction. The Projectmap block diagram is also used in marketing to show roadmaps and can represent any set of activities over a timeline – e.g. process or recipe.
Contents Projectmap 1 Development 1 Values and Principles 2 Example 3 Further applications 5 See also 5 External links 5
Development The Projectmap methodology was developed following the increased use of spreadsheets in project management, alongside task management tools and mind maps. These trends suggested an abandonment of traditional, Gantt based project management tools and a need for a new method of presentation of activities over a timeline. The first project management articles and Projectmap templates became available online in April 2017. Web applications technologies like Angular2.0 and React/Redux became widely used several years before the new Projectmap diagram was developed and enabled implementation of some of the major visualization and multi user concepts in today’s Projectmap implementations . The first tool using Projectmap diagram went into Beta sessions in June 2017, under the name “Proggio”.
Values and Principles Values
• Team engagement as a prerequisite for project success • Project visualization over detailed plans • Intuitive planning over project engineering • Areas of activity over task hierarchy • Confidence indicators as KEY project sensors
• A good project diagram must be presented coherently on a single page • A project is a social event before it is a technical challenge. Thus, the key to project success lies in paying attention to the people and measuring their engagement level • The intuitive way people grasp the project should dictate the project diagram design • Intuitive planning is based on Areas of Activity and Activity Sequences • Working with areas of activity enables automated project analysis • Activities shouldn’t be linked hastily to create dependencies. Most of the activities can be done in parallel • Risk calculations will never be as accurate as risk perception. Therefore, the team’s risk perception is critical for developing a risk avoidance plan • A project plan is incomplete without an indicator that can point at the success rate of the project, based on the data included in the plan
Example In the following table there are three categories, labeled A through C. Some activity chains are built into the planning layer of the Projectmap. High level activities are used to show high-level project plans. The “Details” layer activities breakdown Planning layer “Containers” into smaller tasks and enable easy task management.
Once the data is captured in this specific manner, a Projectmap can be created:
1. High-Level view
2. Planning view – intermediate layer
3. Details view – breaking down Planning layer containers
Further applications Projectmap can also be used to manage employee timelines, by presenting the employee as “workstream” and list his/her activities over the timeline. Setting up shifts and work schedules can be done in a similar fashion. See also • Critical path method • Float (project management) • projectmap.solutions
External links • Projectmap.solutions
Cite error: Invalid
parameter "group" is allowed only.
<references />, or
<references group="..." />