Worldwide Locations
96 Results Found
How can organizations in diverse industries continue to use familiar waterfall practices and at the same time be more agile? The answer is to use program management that is designed to be agile.
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.
There is a reason why Agile training methods are becoming mainstream. They can work! Although every Agile practice is not necessarily appropriate for every organization, each practice has delivered real value to many organizations, and some Agile practices can be used by anyone!
With Forrester Research declaring "Waterfall processes have become obstacles to speed, quality and predictability," and more than 85% of CIO's surveyed by CIO Magazine using or planning to pursue Agile practices in 2014, this one-hour webinar will explore the basics of Agile and why so many organizations are adopting Agile methods.
The term "life cycle" implies two things: that a process is perpetual and that the sequence of events is obligatory or uni-directional. There is no beginning or end to a life cycle and the sequence of events cannot change. A seed cannot go directly to being a mature plant nor revert back to the blossom stage.
Project procurement activities are often managed by specialists. By this I mean that the procurement department takes over responsibility for purchasing and contract management from the project manager. As a result of this separation of responsibilities, the steps and stages of procurement are often poorly understood by PMs. In this and the next few blog submissions, I will attempt to shed light on procurement activities and relate these activities to the PMI PMBOK.
The tools described in this white paper are essential PM tools. Tools that will best be used, regardless of the project, are the WBS, communication model, and the precedence diagram. The other tools will be needed depending on the project.
If you want to stay relevant as an IT professional, you have two choices: evolve your current skills or make a big change.
Projects are a social endeavor. Traditional project management approaches have shied away from the social advantages a more agile project environment brings. By nature, we are storytelling, pattern seeking and social people. We need colocation to shine truly in a project environment.
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.