https://mediawiki.middlebury.edu/PieMatrix/index.php?title=Special:NewPages&feed=atom&hideredirs=1&limit=50&offset=&namespace=0&username=&tagfilter=&size-mode=max&size=0PieMatrix Wiki - New pages [en]2024-03-29T10:57:21ZFrom PieMatrix WikiMediaWiki 1.35.14https://mediawiki.middlebury.edu/PieMatrix/How_to_get_a_list_of_tasks_for_one_personHow to get a list of tasks for one person2015-04-14T16:10:17Z<p>Corinna Noelke: Created page with "*Go to “My To do” *Click on the gear “More” in the upper right hand side *Choose "View" to determine how you want the tasks sorted, e.g., by start date, end date, proj..."</p>
<hr />
<div>*Go to “My To do”<br />
*Click on the gear “More” in the upper right hand side<br />
*Choose "View" to determine how you want the tasks sorted, e.g., by start date, end date, project order<br />
*Then click on "Filter" and "Filter by Project" and select the specific project or "Filter by Layer" if there are tasks in several layers you want to have listed<br />
*Then go to the drop-down menu next to "Person" to choose the person whose tasks you are looking for<br />
*If you go on the left side to "List" instead of "Date Group" or "Project Group", you then see all tasks for that one person in the order you chose and for the projects/layers you chose<br />
*By clicking on "PDF" in the upper right hand corner, you can create a PDF with all the tasks</div>Corinna Noelkehttps://mediawiki.middlebury.edu/PieMatrix/How_to_Get_a_list_of_tasks_for_one_personHow to Get a list of tasks for one person2015-04-14T16:07:51Z<p>Corinna Noelke: Created page with "- Go to “My To do” - Click on the gear “More” in the upper right hand side - Choose "View" to determine how you want the tasks sorted, e.g., by start date, end date, p..."</p>
<hr />
<div>- Go to “My To do”<br />
- Click on the gear “More” in the upper right hand side<br />
- Choose "View" to determine how you want the tasks sorted, e.g., by start date, end date, project order<br />
- Then click on "Filter" and "Filter by Project" and select the specific project or "Filter by Layer" if there are tasks in several layers you want to have listed<br />
- Then go to the drop-down menu next to "Person" to choose the person whose tasks you are looking for<br />
- If you go on the left side to "List" instead of "Date Group" or "Project Group", you then see all tasks for that one person in the order you chose and for the projects/layers you chose<br />
- By clicking on "PDF" in the upper right hand corner, you can create a PDF with all the tasks</div>Corinna Noelkehttps://mediawiki.middlebury.edu/PieMatrix/Why_PIEmatrix_and_not_Basecamp%3FWhy PIEmatrix and not Basecamp?2015-02-18T12:27:59Z<p>Corinna Noelke: </p>
<hr />
<div>*Basecamp is a list of tasks which allows you to assign other people to tasks, communicate with them, and upload files<br />
*PIEmatrix is all of the above and more:<br />
**It is much more pleasing to the eye<br />
**It allows for complicated projects to be managed across multiple layers to allow for the big picture and at the same time to break it down to the smaller parts the individual users need<br />
**Those smaller parts can be broken up into "slices" and "boxes" (or "chapters" like in a book) - these "chapters" help to conceptualize the different pieces of the project<br />
**It creates process flows<br />
**It is made for repeatable best practices that can improve over time<br />
**It keeps all knowledge from processes so that transition of processes/projects/jobs from one person to another becomes much easier<br />
*PIEmatrix helps you complete your Wish List, Basecamp helps you complete your Task List<br />
*Lots of peoples Wish List is to:<br />
**Improve productivity<br />
**Get more done with the same resources<br />
**Increase revenue or reduce cost<br />
**Keep all knowledge from processes in a place that allows others to pick up the content quickly<br />
=>PIEmatrix can make this happen<br />
*See this detailed comparison of features:<br />
*Static project templates versus dynamic process templates<br />
**Basecamp: Provides project templates. The problem is that these templates are static and can only be used for new projects. Secondly, Basecamp does not allow you to create a new template from a modified project. Third, any step you create in the template can be edited or destroyed by the team member, thus completely changing the standard without any controls or oversight<br />
**PIEmatrix: Provides project process templates (PIE Templates). They are dynamic or static, allowing the project manager to update his or her project process with new best practice content in real time. Pie also allows you to create a new template from a modified project. As an example, your project team can add custom steps to their project from your great template. Some of these custom steps may be super for future like projects. With Pie, you can click one button to extract the project changes and make a new PIE Template for your ongoing improvement process. Finally, any step you create in the PIE Template can be marked as not needed by the project manager, but not by the team member. If a step is marked not needed, you can audit to see what were set to not needed and then learn from the field how to improve your process for future use or to discipline your manager for not following agreed best practices.<br />
*Working with reusable file template documents<br />
**Basecamp: You can add a file template document to the project level, but not to the task list or task level. We believe you cannot organize your files in a hierarchical structure.<br />
**PIEmatrix: You can add file template documents to the project process box, or step level. The team members can choose their template file, make a duplicate, and place it in the Work In Progress folder, where it’s an easy place to work together on the deliverable documents.<br />
*Independent tasks versus collaborative steps<br />
**Basecamp: Main purpose is a task list execution focused. Provides only one level of task grouping, called the To-do List.<br />
**PIEmatrix: Main purpose is process and methodology execution focused. Pie uses the term “action steps” rather than “tasks”. The reason is that an action step is a set of dependent activities of getting things done (see dependencies). They are steps moving towards a desired place. Whereas, a task list with no clear process, is just a list of items that may or may not work well for more complex scenarios.<br />
*Making complexity consumable<br />
**Basecamp: Provides only one level of task grouping, called the To-do List. Not the best solution for moderate to more complex projects since they become long lists making it hard for team members and stakeholders to quickly see where they are in reference of the entire project process. This makes it hard for people to consume complexity.<br />
**PIEmatrix: Provides multilevel grouping of step activities inside a PIE Template. The first level displays the phases (pie slices) of the project. The second level displays the sub- phases or phase milestones (process boxes). These contain the third level, which are action steps for getting the work done. You can then add more levels as needed with sub steps and sub-sub steps. Pie also provides a visual pie view that resembles a continuous improvement circle. You can also stack together multiple PIE Templates together for complex projects. This makes it easy for team members and stakeholders to just select their process area, simplifying the complex project. Novice project managers and team members can easily consume both a simple, moderate, or complex project.<br />
*People roles for fast assignments<br />
**Basecamp: You cannot establish people roles with your project template tasks. Basecamp only allows you to assign real people names to the template tasks. This might fine for some small web development firms where the team is always the same on each project. This is not helpful for larger and more complex organizations, such as an academic hospital.<br />
**PIEmatrix: You can establish people roles with your PIE Template action steps. This is very important since many projects created from the template will have different people involved. We make it easy for you to assign a role, such as “business analyst” to a number of steps. Then when you create a project, all you need to do is assign a person to that role with one click and then that person automatically gets assigned to all of the business analyst duties.<br />
*Know-how and your secret sauce<br />
**Basecamp: You cannot add descriptions to tasks. These means you cannot pre- populate your secret sauce for helping people success faster and better.<br />
**PIEmatrix: You can add descriptions to steps. This is your know-how, your best practice standard guidelines, tips, and useful information to help things not slip through the cracks or get into trouble. Pie is made from the ground up to help you push captured know-how out to the teams and to allow them to help improve future know-how content in real time.<br />
*Planning for dates<br />
**Basecamp: You cannot provide task durations for estimating task date spans. You also cannot link tasks together with dependencies in order to automatically schedule your dates.<br />
**PIEmatrix: You can provide step duration time for estimating your date spans. You can also link your steps together with dependency links. This makes planning fast with auto scheduling.<br />
*Better planning with a Gantt view<br />
**Basecamp: No Gantt view. This makes it visually hard to see how the schedule is mapped out for moderate to more complex projects. Since all completed tasks in Basecamp set the date for the day they are completed, there is no way to tell if you’re on target or not.<br />
**PIEmatrix: Provides a Gantt view in the Planning tab. This makes it easy to visually see how the work is mapped for capacity and utilization. We also allow you to create a snapshot of your schedule for a future baseline comparison with the actual results. This is great for understanding if you will meet your targeted project’s end date. You can also use this information to better plan future projects.<br />
*Know-how at your fingertips<br />
**Basecamp: As explained in the Planning section, the team members will not have information at their finger tips to know how to best execute their work for faster and higher quality success since there is no way to contain step description. However, the team members do have a page where they can see all of their to-dos for the week. We haven’t been able to find a way for an individual to add a personal to-do that is not tied to a project. Not sure if this can be done.<br />
**PIEmatrix: Your team members and stakeholders will have all of your best practice information at their fingertips while they work in real time. This is a key power of Pie. On a similar note, Pie also has a personal To-do page. Each person will have the ability to set his or her My To-do page with different filtered views, such as group by date, group by project, or group by list. The group by list is similar to Basecamp’s display. The group by date is the most productive and is not available in Basecamp. A team member or stakeholder can manage and execute all of their work directly from this page without ever needing to go to another page. Also, the individuals can add their own private to-do without it being associated to any project. This is helpful for personal day-to-day workload management.<br />
*Collaboration with message posting<br />
**Basecamp: Great collaboration features for posting comments. You can reply to an email and have that information show up in the task news feed. You can even add a non- user’s email to a post and have that person get the message. One problem when commenting back and forth is that Basecamp doesn’t automatically push the new message to your page while you are chatting. You have to refresh the page. At least, that’s what we experienced.<br />
**PIEmatrix: We too have great posting features. We invested the past year and a half of developing a new set of social features that resemble Basecamp messaging across action steps. Soon you will have the ability to also reply back from emails to have them post inside Pie step news feeds. You will also be able to add non-Pie users to the email stream and route conversations with them via email. All of our news feeds push the changes to the team member automatically without any page refresh needs. In addition, we make it easy for you to notice when new comments are made without having to hunt them down. Our new Social tab has a subtle pulsating indicator that notifies you with new messages, which can be viewed all in one spot.<br />
*Posting issues and solving problems together<br />
**Basecamp: No issue or risk posting or management. This is a big problem unless if your teams never run into issues or risks.<br />
**PIEmatrix: Your team members and stakeholders can post a concern as a special issue or risk posting. This places a red or yellow indicator on the step and also roles up to higher-level views, such as the executive dashboard. The issue and risk log report makes it easy for managers and directors to quickly see open problems. With one click, they can not only read the conversation stream, but also jump in with their own comments to help solve and close the issue or risk item.<br />
*Knowing when to start work to finish it on time<br />
**Basecamp: You cannot set a task’s start date. You can only set its due date.<br />
**PIEmatrix: You can set a step’s start date. With the expected duration as mentioned in the planning section above, the user will see both the start and due dates based on expectations.<br />
*Show in progress work or percent complete.<br />
**Basecamp: A team member or stakeholder cannot set a task as in progress. It’s either not started or completed. That is fine for very small and short tasks that can be done within one day, but if the task takes a few days or weeks, you cannot use this model.<br />
**PIEmatrix: Team members and stakeholders can mark their own steps as in progress and even set percent complete. This is helpful for a few reasons. One it drives the due date of that step since the step will most likely have an expected duration. Secondly, the start date can indicate if the due date will be met or late.<br />
*Don’t mess up my work (privacy controls)<br />
**Basecamp: When a team member or a stakeholder is given access to a project, that person can edit anyone else’s task.<br />
**PIEmatrix: When a team member or a stakeholder is given access to a project, the project manager can decide on the spot if that person can only edit his or her own step or have the ability to edit others with a role called Project Administrator. In addition, there are other permission and visibility settings that the administrator can set up for a new user, such as executive read-only view across a department, a project creator, or a PIE Template content author.<br />
*Let me know when I’m up next (workflow notification)<br />
**Basecamp: No workflow capabilities. No use of task dependencies.<br />
**PIEmatrix: You can establish workflow capabilities that will trigger email notifications to the team members when their work is now ready to work on. For example, let’s say I have a step called “Document and publish the new process scenario for approval”. The next step is called “Review and approve new process scenario document” and that one belongs to you and the director of the stakeholder department. Once I mark my step done, Pie will automatically send out an email to you saying your step is now ready along with any detail information about how to get it done. Secondly, you can set up the approval step to be a “group step”, that means both you and the stakeholder department director would automatically get your own approval step, so you can each mark your approval separately (automatically created as two substeps).<br />
*Review progress across your portfolio.<br />
**Basecamp: No portfolio view of your projects.<br />
**PIEmatrix: You will have a visual dashboard showing what is going on in real time. The color indicators (green, yellow, and red) will provide a quick-glance visual on where are the successes, risks, and failures. A project manager can manage his or her set of active projects from the dashboard. The progress bars and milestone dates show where they are. Executives and stakeholder directors can have messaging conversations with the project manager directly from the dashboard portfolio progress or issue log pages. They will have multiple ways to set up personal filters so the next time they log in, they can quickly access their personal dashboard view<br />
*Drill down, make decisions, and take action.<br />
**Basecamp: No portfolio progress view. You basically work on open to-dos at the task level. This can be too much information in the Basecamp calendar where there are 7 managers running 50 projects with 500 participants.<br />
**PIEmatrix: You can view the high-level portfolio view. You can review project data information, such as project budget, or relative priority. You can review the more complex projects with a one-click detail view. This page can show a complex project with multiple process steams from a stacked PIE Template. If you want to go further, just click again to open the project and review the high, medium, and low-level progress indicators throughout the project.<br />
*Keep our departments separate.<br />
**Basecamp: No ability to structure business units<br />
**PIEmatrix: You can establish business unit structure for managing visibility across your enterprise. An executive in the one department, such as Continuous Improvement group would see all projects in that unit. However, the IT executive will not be able to see those projects unless that person is either assigned to this business unit or is part of a higher level parent business unit. Your organization will define how to set this up.<br />
*Provide the best resources to help your team be successful<br />
**PBasecamp: Self training. Self help. No real person training. No real person support help.<br />
**PIEmatrix: We offer not only good ways for self training and self help via our robust online Help Center, but we also can provide an onsite train-the-trainer program where a live person will come to your door and help your key people become experts with features, know how to strategically use our platform, and learn how to train other people within your organization. We offer free phone and chat support along with email support. We are Vermonters and we work to build Vermont jobs.</div>Corinna Noelkehttps://mediawiki.middlebury.edu/PieMatrix/What_goes_into_the_PIEmatrix_Wiki%3FWhat goes into the PIEmatrix Wiki?2015-02-18T12:27:15Z<p>Corinna Noelke: Created page with "Some examples of content are: *What are the benefits of using PIEmatrix *How to get a PIEmatrix account *How to start a project *Examples of what PIEmatrix can be used for *Wh..."</p>
<hr />
<div>Some examples of content are:<br />
*What are the benefits of using PIEmatrix<br />
*How to get a PIEmatrix account<br />
*How to start a project<br />
*Examples of what PIEmatrix can be used for<br />
*What a department should be mindful of when using PIEmatrix</div>Corinna Noelkehttps://mediawiki.middlebury.edu/PieMatrix/Wiki_Edit_HelpWiki Edit Help2014-12-05T17:05:38Z<p>Corinna Noelke: Created page with "* You may wish to use your userpage (click on your name at the top when logged in) to practice or "test" new content to make sure it looks good, before copying and pasting it ..."</p>
<hr />
<div>* You may wish to use your userpage (click on your name at the top when logged in) to practice or "test" new content to make sure it looks good, before copying and pasting it elsewhere.<br />
* [http://en.wikipedia.org/wiki/Help:Cheatsheet Wiki Cheatsheet]<br />
* [http://meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software.<br />
* [http://www.mediawiki.org/wiki/Manual:Configuration_settings Configuration settings list]<br />
* [http://www.mediawiki.org/wiki/Manual:FAQ MediaWiki FAQ]<br />
* [http://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]</div>Corinna Noelkehttps://mediawiki.middlebury.edu/PieMatrix/Need_Technical_Help_with_your_Project%3FNeed Technical Help with your Project?2014-12-05T17:05:06Z<p>Corinna Noelke: Created page with "PIEmatrix provides the best resources for technical questions about PIEmatrix use so you can get help when you need it: *Videos: Most pages have a link to a video on the upper..."</p>
<hr />
<div>PIEmatrix provides the best resources for technical questions about PIEmatrix use so you can get help when you need it:<br />
*Videos: Most pages have a link to a video on the upper right-hand side (white area) with a video specific to the page you are on.<br />
*Tips: Most pages also have "Tips" which explain the main parts of a page right next to the video link<br />
*Help Center: Click on "Help" on the upper right-hand side for access to the software's own Help Center<br />
*Live Chat: the link can be found at the bottom right of the Help Center when you are logged into PIEmatrix.com<br />
*Phone support: 802.318.4891<br />
*Email support: [mailto:support@piematrix.com support@piematrix.com]</div>Corinna Noelkehttps://mediawiki.middlebury.edu/PieMatrix/What_your_Department_should_discuss_before/when_using_PIEmatrixWhat your Department should discuss before/when using PIEmatrix2014-12-05T17:04:28Z<p>Corinna Noelke: Created page with "*Tags: agree on the tags. They act as the keywords by which you search for a project. Be mindful not to use for example HR and Human Resources. When searching you would need t..."</p>
<hr />
<div>*Tags: agree on the tags. They act as the keywords by which you search for a project. Be mindful not to use for example HR and Human Resources. When searching you would need to remember to search for both HR and Human Resources to find all projects that relate to Human Resources. Also be mindful of spelling - tags cannot be deleted...<br />
*Naming of Projects: If you have a numbering convention or naming convention that you are using for your projects or do not have one yet at all - make sure everybody in your department knows the preferred naming method, e.g., by employee number, by project number, by area to which project belongs, etc.<br />
*Naming of Roles in Templates: it might be best to create role names that have a common theme at the beginning, e.g., HR Benefits Specialist, HR Retirement Specialist, HR... so that all roles related to your area show up together when you are assigning roles to steps, this will make the role assigning much faster<br />
*More on Roles: you are setting up a template because you will use this process again - imagine that people involved in the project change - now come up with a name for the type of person who will do this step no matter whether this year it is Sarah who is doing these steps and next year it is John because Sarah moved on - you want to have a name for the role that makes it clear what type of person should be assigned to this task</div>Corinna Noelkehttps://mediawiki.middlebury.edu/PieMatrix/Duration_in_Templates_and_how_it_effects_Live_ProjectsDuration in Templates and how it effects Live Projects2014-12-05T17:03:53Z<p>Corinna Noelke: Created page with "*If you update duration in a template for future use, it will not dynamically update any steps that have dates or are either marked in progress or completed. This is a feature..."</p>
<hr />
<div>*If you update duration in a template for future use, it will not dynamically update any steps that have dates or are either marked in progress or completed. This is a feature to prevent any unwanted changes once the work has begun. Dynamic updates only change the not-started steps.<br />
*The duration on a layer is considered more of a “hint” from a schedule perspective, and subject to being overruled as the project develops. So, if the step has dates, a duration set by hand, or progress (In Progress or Completed) the duration in the project will not update when changed in the template.</div>Corinna Noelkehttps://mediawiki.middlebury.edu/PieMatrix/Available_TemplatesAvailable Templates2014-12-05T17:03:17Z<p>Corinna Noelke: Created page with "*PIEmatrix has a "Community" were users have already and can upload templates too. You find the "Community" by clicking on "PIE Templates" on the top and then on "Template Com..."</p>
<hr />
<div>*PIEmatrix has a "Community" were users have already and can upload templates too. You find the "Community" by clicking on "PIE Templates" on the top and then on "Template Community" written in dark blue on the right side<br />
*Whenever you use an existing template in your PIEmatrix instance - be mindful not to change it if other users are using it as well, instead copy it and make the adjustments to this new template that is now 'yours'<br />
*For Middlebury College Users:<br />
**The "EZ PM" template available in each Business Unit has just three slices called "Plan", "Execute", "Close", this is a good start for any new project. If you would like to use this template as a basis to create a new project in the template area, just copy the "EZ PM" template<br />
**There are several calendar based templates for the calendar year or by fiscal year<br />
**There are some imported templates like "Annual Marketing Plan", "Grant Management", "RFP Process"</div>Corinna Noelkehttps://mediawiki.middlebury.edu/PieMatrix/What_do_you_do_in_Templates_vs._Projects%3FWhat do you do in Templates vs. Projects?2014-12-05T17:02:48Z<p>Corinna Noelke: Created page with "Assuming that this is a project you will do again and you thus would like a template that is as good as it gets so that the next time around it will be as easy as pie... to cr..."</p>
<hr />
<div>Assuming that this is a project you will do again and you thus would like a template that is as good as it gets so that the next time around it will be as easy as pie... to create a new project:<br />
*Templates:<br />
**Add / Delete / (Re)name Slices<br />
**Add / Delete / (Re)name Boxes<br />
**Add / Delete / (Re)name Steps and add descriptions to steps<br />
**Changing position of any of above<br />
**Assign roles to the steps<br />
**Update duration of a step<br />
**Set dependencies between steps<br />
**Upload files that are used as templates, instructions, etc.<br />
<br />
*Projects:<br />
**Assign the actual people who will fill the roles assigned in the template (you do this by clicking on the blue "Info" button on the upper right-hand side<br />
**Set dates</div>Corinna Noelkehttps://mediawiki.middlebury.edu/PieMatrix/When_do_you_create_boxes/steps_in_a_template_vs._a_project%3FWhen do you create boxes/steps in a template vs. a project?2014-12-05T17:02:14Z<p>Corinna Noelke: Created page with "*If you are working on a one-time project you would choose a template that suits your needs and then add any boxes/steps on the project level *If you plan to do this project o..."</p>
<hr />
<div>*If you are working on a one-time project you would choose a template that suits your needs and then add any boxes/steps on the project level<br />
*If you plan to do this project over and over again, you ideally create the boxes/steps on the template level as it is the template you would use again for the next time around</div>Corinna Noelkehttps://mediawiki.middlebury.edu/PieMatrix/What_are_Templates%3FWhat are Templates?2014-12-05T17:01:40Z<p>Corinna Noelke: Created page with "*Every Project is based on a template. Each template consists of a pie with one to several pie slices and possibly boxes and steps already added *A very basic template can for..."</p>
<hr />
<div>*Every Project is based on a template. Each template consists of a pie with one to several pie slices and possibly boxes and steps already added<br />
*A very basic template can for example have three slices that are e.g., called "Plan", "Execute", and "Close" without any boxes or steps<br />
*A sophisticated template can involve many slices with each several boxes and steps associated with those boxes.<br />
*A stacked template is template that includes several pies (all with the same amount of slices and names of slices) "stacked" on top of each other</div>Corinna Noelkehttps://mediawiki.middlebury.edu/PieMatrix/How_to_StackHow to Stack2014-12-05T17:01:06Z<p>Corinna Noelke: Created page with "The [https://my.piematrix.com/pie-helpcenter/?s=stack Help Center] has a good explanation. Remember that only layers with the same number of slices which are named the same ca..."</p>
<hr />
<div>The [https://my.piematrix.com/pie-helpcenter/?s=stack Help Center] has a good explanation.<br />
Remember that only layers with the same number of slices which are named the same can be stacked. That means you first create the individual layers, e.g., Department, IT, Vendor, then you create the stacked template. When you need to make changes to the template, make the change to the individual template layer, it will then flow through to your stacked template and your project which uses that stacked template (if you set the project setting to "Dynamic")</div>Corinna Noelkehttps://mediawiki.middlebury.edu/PieMatrix/ExamplesExamples2014-12-05T17:00:32Z<p>Corinna Noelke: Created page with "1st example is the Budget Office's timeline. They have: *monthly tasks that need to happen each month *an annual timeline of tasks that need to happen at certain times of the ..."</p>
<hr />
<div>1st example is the Budget Office's timeline. They have:<br />
*monthly tasks that need to happen each month<br />
*an annual timeline of tasks that need to happen at certain times of the year, e.g., Board materials need to be prepared quarterly, a government report is due at a certain of the year, etc.<br />
*the actual budget creation timeline<br />
In order to see how the different steps in each of the three timelines effect steps in one of the other timelines, the Budget Office created a "Stacked" Template (and project)<br />
<br />
2nd example is a Software Implementation project. There are steps that need to be done by:<br />
*IT<br />
*the department getting the new software<br />
*the vendor<br />
Steps for all three areas happen often simultaneously and are dependent on each other. So that it does not become confusing, IT, the Department, and the Vendor each get their own layer. Then these three layers are stacked into one project. This allows to create dependencies between steps done by IT vs. the Department, etc. It also allows to see the overall progress of the project. Last but not least, as you work on 'your' steps, you can just look at the layer that concerns you and your view is not cluttered by what the other 2 areas need to do</div>Corinna Noelkehttps://mediawiki.middlebury.edu/PieMatrix/Stacking_of_ProjectsStacking of Projects2014-12-05T16:59:55Z<p>Corinna Noelke: Created page with "If you have several processes/projects going on that belong together but each has too many steps to put them all into one layer, you can stack the projects."</p>
<hr />
<div>If you have several processes/projects going on that belong together but each has too many steps to put them all into one layer, you can stack the projects.</div>Corinna Noelkehttps://mediawiki.middlebury.edu/PieMatrix/Issues_versus_RisksIssues versus Risks2014-12-05T16:59:19Z<p>Corinna Noelke: Created page with "*Risk is an uncertain event, that if materialized, could alter the course of a project. Or if it materializes, it becomes a real issue. => set up a mitigation plan to help avo..."</p>
<hr />
<div>*Risk is an uncertain event, that if materialized, could alter the course of a project. Or if it materializes, it becomes a real issue. => set up a mitigation plan to help avoid a risk from turning into a real and actual problem, aka an issue<br />
*Issue is an actual event that has happened or is in the process of happening that is altering the course of a project until resolved. => solve it ASAP</div>Corinna Noelkehttps://mediawiki.middlebury.edu/PieMatrix/Some_Editing_SuggestionsSome Editing Suggestions2014-12-05T16:58:42Z<p>Corinna Noelke: Created page with "#When you start a new project, it might be easiest to first think about the major pieces of your project - make those into Boxes #Write down the steps you have in mind, add th..."</p>
<hr />
<div>#When you start a new project, it might be easiest to first think about the major pieces of your project - make those into Boxes<br />
#Write down the steps you have in mind, add the first step, write down the step, hit enter, write the next step, hit enter, etc.<br />
#When the steps start falling off your screen, think about creating a new Box to break down the steps into manageable chunks<br />
#Re-read your steps, order them so it makes sense to you, then assign people (when you are working in Projects) or roles (when you are working in Templates) by opening the first step, assigning the person/role. Then notice the little blue arrows on the bottom of the wizard which allow you to move to the next step to assign a person/role, move to the next step, etc.<br />
#Think about duration of a step, again click on the first step and edit the duration, then move down within the wizard to the next step. Duration should take into account not just how long the task takes but how long it will realistically take for somebody to get to it, do it, let you know that it is done - this means a 20 min tasks might need a 5 day duration...<br />
#Are there steps that are dependent on a different step? Set that dependency by clicking on the Link when you hover over the step that is dependent on a different step; if the steps are sequenced, i.e., Step 1 needs to be done for Step 2 to happen which needs to be done for Step 3 to happen etc., then you can "Sequence" all the steps in a box by clicking on the gear in the lower right-hand corner of the box and clicking on "Sequence Steps"<br />
#Are there any documents or links you'll need? Add them by clicking on "Files" when you hover over the appropriate step<br />
#Last, but not least, when you are in a Project (not a template), go to the "Planning" tab (on the right side) and start planning by entering dates, make sure to click on the first slice so that no boxes can be seen, that will ensure that you see all steps in all slices and all boxes when you are planning the timeline for the entire project</div>Corinna Noelkehttps://mediawiki.middlebury.edu/PieMatrix/Layers_versus_Pie_Slices_versus_Boxes_versus_StepsLayers versus Pie Slices versus Boxes versus Steps2014-12-05T16:58:07Z<p>Corinna Noelke: Created page with "*Layers: the round pie that you see when you open a template or project. If you stack a project, you stack several layers (of pie) on top of each other *Pie Slices: are the ph..."</p>
<hr />
<div>*Layers: the round pie that you see when you open a template or project. If you stack a project, you stack several layers (of pie) on top of each other<br />
*Pie Slices: are the phases or stages of the process/project, e.g, Plan, Build (or Execute), Close or January, February, March, etc.<br />
*Boxes: contain action steps, they help you organize steps into groups to make your processes/projects easier to navigate and more efficient to complete; think of them as the chapters in a book<br />
*Steps: these are the actionable tasks for you to do, you will track your progress in a process/project by showing that a step has not started yet, is in progress (to varying degrees), is completed, or is not needed after all</div>Corinna Noelkehttps://mediawiki.middlebury.edu/PieMatrix/Getting_StartedGetting Started2014-12-05T16:57:18Z<p>Corinna Noelke: Created page with "#Go to projects, click on project list, you'll see a "Create Project" button createprojectbutton #Click on the "Create Project" button and a wizard o..."</p>
<hr />
<div>#Go to projects, click on project list, you'll see a "Create Project" button [[File:open project.jpg|createprojectbutton]]<br />
#Click on the "Create Project" button and a wizard opens[[File:Project Wizard.jpg|220px|projectwizard]]<br />
#Name the project<br />
#Choose the right business unit in which you are working<br />
#Choose "Draft" mode, this will allow you to play with the project without any team members receiving notifications<br />
#It is a Best Practice to include a description of the project<br />
#Click next and choose a template, a basic template is EZ PM (your area), it has just three slices called "Plan", "Execute", "Close"<br />
#Drag people into the roles: you are likely the "Project Manager", the "Project Administrator" might be your supervisor, include in "Team" everybody you think will be involved in this project<br />
#Click next - for most projects the defaults work fine<br />
#Click next - add tags that will help you find the project, these should be keywords like FY15, Name of Area this project is in, etc., be mindful of spelling, tags cannot be deleted<br />
#Click next - defaults are fine for most projects<br />
#Click create - the project gets created and you'll be asked whether you want to open the project<br />
#Note: at any given time the parameters entered into the wizard can be changed by going to the blue info button in the upper right-hand corner when you are in the project [[File:Infobutton.jpg|infobutton]]</div>Corinna Noelkehttps://mediawiki.middlebury.edu/PieMatrix/Log_Out_TimerLog Out Timer2014-12-05T16:56:04Z<p>Corinna Noelke: Created page with "Under "My Preferences - Application" you can set how long it takes for PIEmatrix to log you out"</p>
<hr />
<div>Under "My Preferences - Application" you can set how long it takes for PIEmatrix to log you out</div>Corinna Noelkehttps://mediawiki.middlebury.edu/PieMatrix/Email_SettingsEmail Settings2014-12-05T16:55:32Z<p>Corinna Noelke: Created page with "*You can set whether you would like to receive notifications from PIEmatrix immediately or in a digest the next day *Go to Settings in the upper right-hand corner. Clicking on..."</p>
<hr />
<div>*You can set whether you would like to receive notifications from PIEmatrix immediately or in a digest the next day<br />
*Go to Settings in the upper right-hand corner. Clicking on "Settings" will open a new tab in the browser.<br />
*On the left side bar choose "My Preferences - Email"<br />
*By clicking on the blue triangles next to, e.g., "Social Notifications", all options are displayed<br />
*Click on "Edit" on top of the page and edit as you see fit<br />
*Note the "Task Due Notifications" on the bottom as well which govern the daily update email from PIEmatrx</div>Corinna Noelkehttps://mediawiki.middlebury.edu/PieMatrix/PIEmatrix_Login_and_UsePIEmatrix Login and Use2014-12-05T16:54:55Z<p>Corinna Noelke: Created page with "*Once your PIEmatrix account has been created, you will receive an email from PIEmatrix with a temporary password. *Go to [http://www.piematrix.com Piematrix website] and log ..."</p>
<hr />
<div>*Once your PIEmatrix account has been created, you will receive an email from PIEmatrix with a temporary password.<br />
*Go to [http://www.piematrix.com Piematrix website] and log in using your full email address with which you registered.<br />
*At Middlebury College this would be (xxxxx@middlebury.edu) or (xxxxx@miis.edu) and your assigned password.<br />
*When you log in with that password you will be asked to change your password.<br />
*PIEmatrix works on all browsers.<br />
*PIEmatrix requires Adobe Flash to be installed.</div>Corinna Noelkehttps://mediawiki.middlebury.edu/PieMatrix/Usage_PolicyUsage Policy2014-12-05T16:54:14Z<p>Corinna Noelke: Created page with "*Be mindful of the information contained in files that are uploaded into PIEmatrix *At Middlebury College be mindful of the following policies: [http://www.middlebury.edu/offi..."</p>
<hr />
<div>*Be mindful of the information contained in files that are uploaded into PIEmatrix<br />
*At Middlebury College be mindful of the following policies: [http://www.middlebury.edu/offices/technology/infosec/governance/PCI Payment Card Industry Data Security Standard] and the [http://www.middlebury.edu/offices/technology/infosec/governance/DCP Data Classification Policy]</div>Corinna Noelkehttps://mediawiki.middlebury.edu/PieMatrix/At_Green_Mountain_Higher_Education_Consortium_SchoolsAt Green Mountain Higher Education Consortium Schools2014-12-05T16:53:22Z<p>Corinna Noelke: Created page with "*At Middlebury College contact [mailto:noelke@middlebury.edu Corinna Noelke] *At Champlain College contact [mailto:mulhall@champlain.edu Tee Mulhall] *At Saint Michael's Colle..."</p>
<hr />
<div>*At Middlebury College contact [mailto:noelke@middlebury.edu Corinna Noelke]<br />
*At Champlain College contact [mailto:mulhall@champlain.edu Tee Mulhall]<br />
*At Saint Michael's College contact [mailto:JTrottier@smcvt.edu Joann Trottier]<br />
*Any Faculty, Student, and Staff can get a PIEmatrix account. If you would like to work with outside vendors on projects in PIEmatrix, they can be set up with a PIEmatrix account as well.</div>Corinna Noelkehttps://mediawiki.middlebury.edu/PieMatrix/Any_Interested_UserAny Interested User2014-12-05T16:52:36Z<p>Corinna Noelke: Created page with "Any interested user can get a Free Trial by clicking on the button on the [http://www.piematrix.com PIEMatrix website] button."</p>
<hr />
<div>Any interested user can get a Free Trial by clicking on the button on the [http://www.piematrix.com PIEMatrix website] button.</div>Corinna Noelkehttps://mediawiki.middlebury.edu/PieMatrix/Sample_PIEmatrix_ProjectsSample PIEmatrix Projects2014-12-05T16:51:57Z<p>Corinna Noelke: Created page with "*Creating a new Project Proposal *RFP *Your departments annual task list *A complex long-term process such as creating the company's budget, tax due diligence, annual benefit ..."</p>
<hr />
<div>*Creating a new Project Proposal<br />
*RFP<br />
*Your departments annual task list<br />
*A complex long-term process such as creating the company's budget, tax due diligence, annual benefit enrollment, Website updates (tracking updates and postings that need to happen throughout the year)<br />
*Meeting calendar with steps that remind you of best practice meeting prep, meeting after work...</div>Corinna Noelkehttps://mediawiki.middlebury.edu/PieMatrix/Why_PIEmatrix_and_not_my_xls/doc/tasks_etc._list%3FWhy PIEmatrix and not my xls/doc/tasks etc. list?2014-12-05T16:51:08Z<p>Corinna Noelke: Created page with "*Excel is made for math formulas and data, word is for writing, PIEmatrix is for running projects and processes.... *We are all very visual - **PIEmatrix gives you the to-do l..."</p>
<hr />
<div>*Excel is made for math formulas and data, word is for writing, PIEmatrix is for running projects and processes....<br />
*We are all very visual -<br />
**PIEmatrix gives you the to-do list if you want it AND it helps you to visually break up the process into "chapters" that help to conceptualize the different pieces of the project<br />
**It is much more pleasing to the eye<br />
*Dependencies - We need to know what needs to happen before we can do the next step - PIEmatrix allows you to create dependencies of steps AND sends you an email when your step can be done, i.e., the steps it is dependent on have been completed<br />
*We might need additional documents - PIEmatrix allows us to upload those files (or links) so that we don't have to search for them in our email, the server, ...<br />
*Nobody likes nagging - PIEmatrix reminds others (and you) when steps are due so you don't have to remind them<br />
*Collaboration - Excel or Word etc. are not collaborative; you cannot even work in them at the same time (unless you use google docs)<br />
*Repeated use - Pie is made for repeatable best practices that can improve over time, xls/doc lists are not<br />
*Manage workload - PIEmatrix shows the to-do's for each member in your group AND allows you to plan the project looking at the timeline and who has to do what in any given timeline<br />
*[[File:pie vs excel.jpg|pievsexcel]]</div>Corinna Noelkehttps://mediawiki.middlebury.edu/PieMatrix/What_to_use_PIEmatrix_forWhat to use PIEmatrix for2014-12-05T16:50:27Z<p>Corinna Noelke: Created page with "Think of all the great knowledge your organization has. You may have lots of goodies stored on the servers, in people’s e-mail folders, and in their heads. You may feel conf..."</p>
<hr />
<div>Think of all the great knowledge your organization has. You may have lots of goodies stored on the servers, in people’s e-mail folders, and in their heads. You may feel confident that your firm has standard processes, but are they instantly accessible?<br />
<br />
There are three common problems. 1) is not having a good way to get this knowledge out of people’s heads and into a central standard system. 2) is not having this great knowledge someplace so it’s instantly accessible at your employee's fingertips. 3) is not being able to repeat it.<br />
<br />
What’s needed is a smart and dynamic place for your knowledge. It needs to be easy for your teams to get instant access to the details of how to get work done well and why they are doing it. Once this is in place, then it’s a matter of setting up sessions for the subject matter experts to migrate their knowledge into the central system. The process knowledge should be stored contextually with the action steps. For example, PIEmatrix provides a way to store detail knowledge inside each action step object. All the user needs to do is to hover over the step to get a pop up of the process tips and tricks.<br />
<br />
The next part is repeatability and scale: PIEmatrix makes it easy to repeat your set of knowledge content over and over for like-projects and like-business processes.<br />
<br />
Now think of your stakeholders, partners, and end-customer team members. Imagine that they too have instant access to know what to do next. This is powerful!<br />
<br />
Make your accumulated knowledge repeatable so any of your team members in the world can kick off a new project with the latest and greatest know-how.</div>Corinna Noelkehttps://mediawiki.middlebury.edu/PieMatrix/Who_can_contribute_content_to_the_PIEmatrix_Wiki%3FWho can contribute content to the PIEmatrix Wiki?2014-12-05T16:49:34Z<p>Corinna Noelke: Created page with "Anyone. (Individuals watching a Wiki page will receive automatic notification of changes made to Wiki articles. Changes may be reverted at any time.)"</p>
<hr />
<div>Anyone. (Individuals watching a Wiki page will receive automatic notification of changes made to Wiki articles. Changes may be reverted at any time.)</div>Corinna Noelkehttps://mediawiki.middlebury.edu/PieMatrix/Guidelines_for_consistencyGuidelines for consistency2014-12-05T16:48:44Z<p>Corinna Noelke: Created page with "*Users are strongly encouraged to watch Wiki pages with content that relates to their functional work in order to ensure content is accurate and current. *Do not create length..."</p>
<hr />
<div>*Users are strongly encouraged to watch Wiki pages with content that relates to their functional work in order to ensure content is accurate and current.<br />
*Do not create lengthy Wiki articles. Instead, organize content thematically and create links between relevant content using Hyperlinks and Categories.<br />
*Add/update content on wiki stub (incomplete) pages.<br />
*Create a Table of Contents (if page is NOT short) by adding section headings (if the page includes 4 or more sections, add a Table of Contents)<br />
*Assign tags/categories to each page. Categorize carefully and frequently. Check for relevant tags/categories before creating new categories.</div>Corinna Noelkehttps://mediawiki.middlebury.edu/PieMatrix/What_goes_in_the_PIEmatrix_Wiki%3FWhat goes in the PIEmatrix Wiki?2014-12-05T16:47:44Z<p>Corinna Noelke: Created page with "Some examples of content are: *What are the benefits of using PIEmatrix *How to get a PIEmatrix account *How to start a project *Examples of what PIEmatrix can be used for *Wh..."</p>
<hr />
<div>Some examples of content are:<br />
*What are the benefits of using PIEmatrix<br />
*How to get a PIEmatrix account<br />
*How to start a project<br />
*Examples of what PIEmatrix can be used for<br />
*What a department should be mindful of when using PIEmatrix</div>Corinna Noelkehttps://mediawiki.middlebury.edu/PieMatrix/Starting_a_New_ProjectStarting a New Project2014-09-26T14:51:08Z<p>Corinna Noelke: </p>
<hr />
<div>#Go to projects, click on project list, you'll see a "Create Project" button [[File:open project.jpg|createprojectbutton]]<br />
#Click on the "Create Project" button and a wizard opens[[File:Project Wizard.jpg|220px|projectwizard]]<br />
#Name the project<br />
#Choose the right business unit in which you are working<br />
#Choose "Draft" mode, this will allow you to play with the project without any team members receiving notifications<br />
#It is a Best Practice to include a description of the project<br />
#Click next and choose a template, a basic template is EZ PM (your area), it has just three slices called "Plan", "Execute", "Close"<br />
#Drag people into the roles: you are likely the "Project Manager", the "Project Administrator" might be your supervisor, include in "Team" everybody you think will be involved in this project<br />
#Click next - for most projects the defaults work fine<br />
#Click next - add tags that will help you find the project, these should be keywords like FY15, Name of Area this project is in, etc., be mindful of spelling, tags cannot be deleted<br />
#Click next - defaults are fine for most projects<br />
#Click create - the project gets created and you'll be asked whether you want to open the project<br />
#Note: at any given time the parameters entered into the wizard can be changed by going to the blue info button in the upper right-hand corner when you are in the project [[File:Infobutton.jpg|infobutton]]</div>Corinna Noelke