PMI-ACP

Moving the blog to  http://pmiacp4u.blogspot.com

Moving the blog to  http://pmiacp4u.blogspot.com

Moving the blog to  http://pmiacp4u.blogspot.com

Moving the blog to  http://pmiacp4u.blogspot.com

I’m trying to understand the PMI’s new certification for  Agile Certified Practitioners , and what value the PMI brings to managing software development projects using Agile methods. So I bought RMC’s  PMI-ACP Exam Prep Guide  which is written by  Mike Griffiths , a guy who understands a lot about project management and Agile methods, and who has been heavily involved in the PMI-ACP program. How PMI-ACP looks at Risk I started with how the PMI says risk management should be done in Agile projects. Unlike the PMBOK, the PMI-ACP does not treat risk management as a knowledge area. Instead, it integrates risk into the different practice domains and activities in Agile projects, from prioritization to delivery and problem management. The first mention of risk management is in “Value-Driven Delivery”, treating risks as “anti-value” when considering what is important to the customer and the business. Fair enough. Later in the same section there is a discussion of how risks need to be

This post is for  Project Management Institute (PMI)’s Agile Certified Practitioner(PMI-ACP) Certificate . Exam for this certificate is meant to test skills of agile practitioners.  Pre-requisite  for appearing in the exam includes having prior experience in general project management (2000+ hours) and agile specific project management (1500+ hours). Folks having prior  PMP ®  or PgMP ®  automatically satisfy general project management experience and hence need not elaborate the experience while filling the form. Also pre-requisite requires having 21 contract hours earned in agile practice, which could include imparting or participating in agile training [Certified Scrum Master (CSM®), In-house agile training, Coaching Client, etc.] My experience of the exam includes following tips 1. This exam tests knowledge on tools, techniques, processes, artifacts, etc. of those practicing agile. It includes knowledge on Scrum, XP, Kanban & Lean including each of the ter

Agile Tooling Agile Tooling refers to hi-tech or low-tech software or artifacts designed to increase the sense of team and to encourage participation among the members. Examples include version control software, collaboration software, or video conferencing for distributed teams. wireframe A wireframe is a "low fidelity” prototype. This non-graphical artifact shows the skeleton of a screen, representing its structure and basic layout. It contains and localizes contents, features, navigation tools and interactions available to the user. It is often used as a communication tool serving as an element of conversation and confirmation of Agile user stories. Domain Model Domain Model illustrates: the business structure, its entities, and their relationships . supply system A supply system where items are produced at the request of the customer is called a Pull System. Ethnocentrism An attitude that one's group is superior to others is called an Ethnocentrism.