A set of techniques to examine and describe the gap between current performance and desired future goals.
TOOLS TRAINING LIVE WEBINARS USER-GENERATED
|Books Events Links White Papers Wikis|
|Language:||All English Arabic French Japanese Korean Portuguese Romanian Russian Spanish|
|Access:||All Free Premium|
|All A B C D E F G H I J K L M N O P Q R S T U V W X Y Z|
11 items found
[This Article Provided Courtesy of PMI]
Overt resistance is easier to handle than behavior that appears to be cooperative, but which prevents the project from moving forward. This article focuses on resistance to business requirements elicitation and discusses how building relationships and trust can help overcome it.
It’s hard to find a use case that is tougher than bringing DevOps tools, processes and culture to bear on a company that centers around building physical devices--large and small. But that's precisely the journey Alan Schachtely, director of software engineering at GE Software, described in a recent presentation.
This handy guide gives you a wealth of ready-to-use tools, checklists, tips and more to help you complete your assignment on time and with the desired results.
Need a concrete example of how to get started with acceptance-test driven development on an existing code base? It is part of the solution to technical debt.
The goal of the global project management community is to advance ideas and create new ones by sharing an open platform for creativity by fostering an environment of collaboration and innovation. The following questions are addressed here: (1) What project management sites are currently available to the public? (2) What architecture is necessary to sustain a global project management community? (3) Why is a global project management community essential?
A technique used to formulate specific targets for achieving an objective at a point in time. A goal is thus an operational transformation of one or more objectives. Goals can be set for enterprise-wide objectives, project objectives, activity-level, and/or quality-related objectives (see Objectives Setting).
Visual specifications are a powerful way of increasing our understanding of requirements and increasingly help us determine if our intended solution will solve the problem and be usable.
Ground rules establish how meetings will be run, how team members are expected to interact, and what behaviors are acceptable & unacceptable. Establishing ground rules is a proven technique to promote acceptable behaviors by minimizing confusion and misunderstandings. Employing ground rules may increase productivity and employee satisfaction. Ground rules aid in cooperation and help bring the team together.
The GRPI model was first introduced by Richard Beckhard (1972) and highlights the different aspects of team cooperation by identify goals, clarifying roles, responsibilities and processes and the interpersonal relationships of team members.