Filtered by:

Clear All
1 2 3 4 5  ... 
10 Golden Rules for working with MS Project View Abstract

Rule 1:  Define Project Start in “Project - Project Information“ Rule 2:  Define Task Type in “File - Options” Rule 3:  Follow Black-Box-Principle Rule 4:  Let Project calculate - Do not edit Dates! Rule 5:  Use Milestones for specific Events and Dates Rule 6:  Use “Deadlines” instead of Constraints Rule 7:  Avoid open ends for Summary Tasks Rule 8:  “Highlander“ Principle – one Task, one Resource Rule 9:  No Work Resource Assignments on Summary Task level Rule 10:  Update Project at Status Date

10 reasons your CEO will thank you for upgrading to the latest Microsoft Project
  • by Raja Noori, Microsoft 
View Abstract

Discover the Project 2013 value pillars and explore the differences between older versions with a focus on high-value business processes. Improvements in scheduling, reporting, resource management, communication and collaboration will be highlighted in the context of driving project value through Project and Office 365.

Adding objectivity and rigor with portfolio analysis and optimization using Project Online and Project Server 2013
  • by Luke Humphrey, Microsoft Corporation and Prasanna Adavi, EPMA Inc. 
View Abstract

In this session we'll walk trough business driver definition, prioritization methodoligies, project-driver impact rating, constraint and resource analysis. The process adds a layer of objectivity and rigor to project selection, and forces key strategic conversation between leadership and relevant stakeholders.

Advanced Task Mode: Manually Schedule vs. Auto Schedule, How Hard Can It Be? View Abstract

Manually Scheduled task mode is one of the most significant enhancements made in recent history. With this enhancement, project managers have the power to choose whether tasks will be scheduled in Manually Scheduled mode or Auto Scheduled mode, Microsoft Project’s native mode of operation. As simple as the choice may seem, some very real implications to managing projects reside in this decision. Are there best practices? Should all tasks be Manually Scheduled? Now that a few years have passed since its inception, is Manually Scheduled mode deemed an effective method of scheduling tasks? Is Auto Scheduled a more preferable method? During this session, best practices learned through years of in depth study, and through working with numerous clients in regards to Manually Scheduled mode will be discussed, and questions will be answered. Please join Dan Renier from Milestone Consulting Group for an advanced session on the use of Manually Scheduled mode. To gain a more comprehensive understanding of Manually Scheduled mode, and how it applies to your projects, plan to attend this session!

Advancing Project Management Maturity @ Microsoft IT View Abstract

IT in any organization is complex and resource constrained. It is often responsible for ensuring things work really well. Employees, partners and customers must be delighted with right level of service while information stay secure and systems are resilient. Project management is crucial to make this happen. In this session, we will take you through the journey of how project management is evolving within Microsoft IT; IT’s experience of adopting Microsoft Project both on premise as well as the online solution. We will address the Project Management focus areas, architectural decisions, technology solutions, deployment, integration, change management and readiness. We will share how we are addressing some of the associated challenges to advancing the Project Management maturity at Microsoft IT.

Allegan Case Study - Best Practices for Expanding Project Server across Your Organization View Abstract

Come hear how Allergan Inc., a multi-specialty health care company, first launched Project Server 10 years ago for one department and has since expanded to six departments. This session draws on firsthand lessons learned at Allergan. This session will benefit anyone interested in learning: • How has Allergan kept Project server relevant and beneficial for a decade? How do they build awareness from one department to the next? • Should my organization expand Project Server? What are the benefits? • What should you consider before, during, and after you expand to additional users? • How should we handle a new department on Project Server? Is it best to create a new Project Server instance for a new department? What are the options? What is the decision process for choosing the best option? • What are the best practices for onboarding a new department to Project Server? Is the onboarding process repeatable? • What’s needed to support multiple departments on Project Server? • Are there any must-do’s or do not do’s? If your organization has multiple departments with current or future interest in Project Server don’t miss this session.

Apps for Project - Top 10 success factors View Abstract

Roadmap from start to store Apps for Office and Apps for SharePoint provide the infrastructure to extend the functionality in Project, Project Server and Project Online.  Using in-house development experience, your organization can create and market solutions to a much larger potential audience.  However, providing applications that will be available through the Office Store requires careful consideration throughout all aspects of the application lifecycle. Proper design is the foundation of a successful app. Carefully consider the value that the applications provide and how that value can be delivered using well established interaction patterns and user interface guidelines. Care must also be taken while developing applications. Apps for Office and Apps for SharePoint introduce a new technical platform for the development of Project applications. We need to understand these new technologies and embrace the challenges and benefits that they will introduce. Once our applications are ready, we need to make them available through the Office store. A proper submission  allows applications to get to the store quickly and be presently in the most effective manner possible. The work does not end once your application becomes available in the Office store. Effort are still required to introduce the application to the PPM community and to provide continuing support and enhancements of the applications. We will discuss our experience bringing application to market and the key factors to their success 1. Understand 2. Experiment 3. Build the right apps 4. Know your audience 5. Consider usability 6. Update skills 7. Build the environment 8. Push boundaries 9. Publish to Office Store 10. Support and enhance apps

Automate Financial Tracking & Variance Analysis View Abstract

For many PMOs, status reporting is an arduous process which requires too much time to manually collect data and build reports instead of analyzing the portfolio and taking corrective action. In this session, learn how UMT360’s integrated Status Reporting module can automate tracking and performance measurement across your portfolio helping you proactively identify early warning indicators and reallocate funds.  You’ll have an opportunity to see how UMT360 helps organizations manage reporting periods, sync actual costs from ERP systems, forecast remaining costs, derive real time variances and automatically create insightful reports and dashboards.

Automating your Project Archival Process with Project Server 2013/Project Online Workflows View Abstract

A common need requirement for any Project Server Implementation is to set up a process for Project Archival, after the project is complete. However, this is generally a manual activity, which becomes cumbersome if your Project Server Implementation houses projects from all parts of the organization (as opposed to just the PMO). If you are using the Project Sites to collaborate, the process of archiving your documents and organizing them becomes even more complex. Automation is possible for the most part of this process, if not all steps, using Workflows. With Project Server 2013/Project Online, you can now use Visio 2013 and SharePoint Designer 2013 to develop these workflows, without the need for coding. This demo rich session intends to cover an end-to-end process of developing a workflow for Archiving Projects. The Scenarios we will cover will include, but not limited to:  • Monitor Project Closure, and after a certain 'retention' period, alert Admins when projects are ready for archiving  • Steps to remove the project from databases that are not applicable (some steps may be manual)  • Run a Site Workflows to migrate the documents in the Project Site to a Central Repository that will act as a Central Document Hub.,  • Set up Content Organizer to automatically sort all the documents to appropriate library in the reporsitory.  • Delete the associated Project Site

AWESOME user experience for Project Web App from a great visual design View Abstract

"Have you ever thought about changing the main page of Project Web Access, but got stuck in the proces? In this session you will learn how easy it is to customize your PWA simply by using PowerPoint and standard web parts in SharePoint. The results are beautiful and does not need any coding. The session will be presented by two consultants from the Danish Project Partner - Projectum. "

1 2 3 4 5  ...