Resource Library

Effective requirements collection at the outset of the project is the key step that will ensure that the project manager can deliver what is actually expected. In this respect, the business analyst must become a key ally and advisor to the project manager. Most project managers are not trained business analysts, so taking advantage of the skill set that a business analyst can offer can greatly enhance the possibility of project success.

UFFA, which stands for “Use it, Flag it or Fix it, Add it,” is the responsibility of every support professional in the knowledge management process. It comes from the Knowledge-Centered Support (KCS) methodology where knowledge management is based on collaboration and a shared ownership of the knowledge base. Let’s break it down.

Today, every project comes with limited resources and an impossible timeline. You have to prioritize, but how do you determine what's most important? The answer is to do more than just prioritize. You have to fully understand your company's strategic direction and make every action align with that strategy. In this hour-long webinar, project management expert Yvan Bastien will show you how to reach that full understanding and make the kinds of informed decisions that lead to success.

Organizations launch projects with the assumption that the new or improved solution will provide worthwhile benefits for stakeholders and a suitable return on investment. By understanding your business requirements you ensure that your teams actually deliver those benefits. Keeping user and functional requirements aligned with the business requirements is a key to successful solution delivery.

Agile is increasingly becoming the foundation for today's business world, and Business Analysts are essential for organizations and projects to achieve maximum success. Following a brief overview, Benjamin will tackle and dispel many of the common myths about Agile and then dig deeper into the true value Business Analysts hold for their organization. Join us for a look at the modern Business Analyst and their role in an Agile environment.

You know you need to invest in training, but how do you get the best return on investment (ROI) from your training dollars? To help you make smart training decisions, we've put together this guide, which illustrates some alternative and little-known payment options, the types of discounts and promotions available with training and a suggested list of courses that give you excellent value.

Enterprise thinking, simply put, is the practice of considering the entire enterprise in decision-making, not just a given group or department. This style of thinking makes the organization both leaner and more agile—lean by reducing the waste and inefficiencies that come from blinkered and siloed thinking and agile by increasing everyone’s understanding of enterprise goals, vision, and functions.

Now that we have looked at the similarities and differences between the first two steps of the military decision-making process (MDMP) and the project management processes from the planning process group that align with them, it’s time to take a look at the third ste...

For a project manager (PM) who has served as a military officer on a battalion or higher staff, the parallels between the military decision-making process (MDMP), the orders production process, and project management doctrine prescribed by the Project Management Institute (PMI) are difficult to ignore. Both the MDMP and the processes outlined in A Guide to the Project Management Body of Knowledge—Fifth Edition (PMBOK® Guide) are iterative in nature, allow for the introduction of changes to the original plan, assign tasks and responsibilities, and involve the concept of managing the scope of the operation or project.

This paper proposes a unifying model for project plans. A distinction will be made between the outputs of project planning and the project plan itself. The significance of this distinction is to allow projects of all types to be described at a high level, in a common language, regardless of the type of analysis used to develop the plan.