Resource Library

Communication is vital within projects and contributes significantly to project success. PMs and BAs have important—and different—roles. Let's take a look.

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.

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.

Agile is a set of principles requiring a significant cultural shift, new paradigms in thinking and team organization. Over the years, Agile has become "productized" or in many cases "institutionalized", creating different flavours and levels of commitment among teams and organizations. Along the way, managers and team members have lost sight of Agile's principles and tried to enforce the use of certain tools and structure where they may not belong. In this one hour webinar, Perry McLeod will explain how tools such as use cases can be successful in an agile environment, provided the principles of agile are always active in the minds of the managers and the team members that are using them. Join Perry to determine whether or not making the cultural shift towards the use case method in an agile environment is the right move for you and your organization.

Enterprises, whether they are commercial, non-profit, or government entities, are operational organizations that operate through the execution of hundreds of processes. The quality of these processes affects every aspect of the enterprise and these processes are rarely static. Business Process Analysis (BPA) is the discipline of examining processes so that they may be changed to align with enterprise objectives.

“Twisted Pair” is another way to identify a network cabling solution that’s also called Unshielded Twisted Pair (UTP) and was invented by Alexander Graham Bell in 1881. Indoor business telephone applications use them in 25-pair bundles. In homes, they were down to four wires, but in networking we use them in 8-wire cables. By twisting the pairs at different rates (twists per foot), cable manufacturers can reduce the electromagnetic pulses coming from the cable while improving the cable’s ability to reject common electronic noise from the environment.

I attended a meeting this week with a customer of mine and a potential new vendor. The new vendor was there to pitch his configuration and setup service offerings for a specific ITSM toolset. My customer has already had one bad experience with an ITSM tool configuration vendor who promised one thing and delivered much less. He ended up with a tool that’s minimally used and not configured to match his business needs. He’s looking for a vendor that can understand his business needs and priorities and quickly help him get his tool configured and working in a short time frame. Then the topic of standard changes came up. My customer asked for examples of standard changes. The vendor responded, “Server reboots are an example of standard changes.”