Skip to main content

PMI Agile Certified Practitioner (PMI-ACP®) Certificate




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® orPgMP® 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 terminologies, ceremonies/meetings, roles, etc. associated with them

2. Its important to be familiar with agile specific principles and keywords including
  • Agile Manifesto
  • Agile Twelve Principles
  • Adaptive Leadership, 
  • Affinity Estimating,
  • Agile Scaling Model
  • Agile Leadership
  • Agile Triangle
  • Agile Earned Value Management (EVM)
  • Definition of Done
  • Burn Down Charts
  • Burn Up Charts
  • Chartering in Agile
  • Collaboration
  • Collocated or Distributed Teams
  • Conflict Types or Levels of Conflict
  • Continuous Integration
  • Cumulative Flow Diagrams
  • Customer Valued Prioritization
  • Emotional Intelligence
  • Empirical Process Control
  • Escaped Defects
  • Exploratory Testing
  • Extreme Programming (XP) including roles, principles, TDD, CI, Pair Programming, etc.
  • Fractional Assignments
  • Information Radiator
  • Internal Rate of Return (IRR)
  • INVEST Model
  • Iteration and Release Planning
  • Lean including process, value, five why's, etc.
  • Kanban including process, principles, task boards, etc.
  • Kano Model
  • Osmotic Communication (Open space or collocation advantage) 
  • Pareto Principle
  • Payback Period
  • Relative Sizing 
  • Refactoring
  • Retrospections
  • Risk Burn Down Charts
  • Risk Exposure
  • Scrum Ceremonies/Meetings (Release Planning, Sprint/Iteration Planning, Daily Scrum Meetings, Sprint Review, Sprint Retrospection)
  • Servant Leadership
  • Signal Card
  • Story points (how to calculate them) 
  • Use Cases
  • Technical Debt 
  • Triangulation
  • User Stories
  • Value Stream Mapping
  • Velocity
3. I have been practicing Agile for 6 years and have digested most of the recommended reference books by PMI for this certification. Having said that when I tried answering the sample questions, was not getting more than 60%. That's when I realized that there are some gaps between practical and standard defined under PMI. After doing some googling, found AgileExams having some good set of questions and brought package of $49 for 9 months. 

4. Have to confess that going through this certification process was definitely beneficial for me as there are lot of things that I learned, which helped me improve upon certain processes that I follow. For example, how to control daily scrum meetings to not exceed more then 15 minutes, how earned value (Cost, Schedule) should be calculated for agile projects, getting familiar with keywords like osmotic communication, triangulation, servant leader, mapping agile values to my current projects, etc. 

5. I spent ~10 hours practicing the exams (short & long) and scheduled the exam in a prometric center, which luckily for me turned out to be less than a mile from my home and was having an opening slot within a day.

6. Allocated exam time is 3 Hours and consists of 120 questions. When I started the exam, I did answer the first question and then instead of 'marking' (middle button), pressed 'review' button (right bottom). It opened the review screen and I missed a beat, phew!!! :). I then went back to the exam screen and being little more attentive this time. After answering initial 2 -3 questions, found my rhythm & confidence and finished the exam within 40 minutes, marking ~10 questions. Took a break for using the restroom and finished reviewing the marked questions in next 5 minutes. I then spent some 1-2 minutes answering survey question about the prometric center and then it came on my screen something like " Congratulations on passing the PMI-ACP® examination"

7. I have prepared some notes on Agile Certified Practitioner exam, similar to my notes on My Notes on PMP® or My Notes on PgMP®, which I will be sharing in my next post. 

Following are some useful links which have free sample tests
1. http://www.agileexams.com/
2. http://starpmo.com/forum/viewforum.php?f=3
3. http://agiletraining.com/2011/09/24/pmi-acp-agile-certification-exam-study-tips/
4. http://pmiacptraining.com/
5. http://whitewaterprojects.com/pmi-acp-sample-exam/#
6. http://www.agiledream.com
7. http://www.proprofs.com/quiz-school/story.php?title=pmiacp
8. http://www.rmcproject.com/pmi-acp/pmi-acp-FreeContent.aspx
9. https://www.keysurvey.com/votingmodule/s180/survey/349789/69ea/
10. https://insite.velociteach.com/pmi_acp_practiceTest_A.aspx

Comments

Post a Comment

Popular posts from this blog

Agile Metrics

Know your business "Done" only tells half the story. It's about building the right product, at the right time, for the right market. Staying on track throughout the program means collecting and analysing some data along the way. In any agile program, it's important to track both business metrics and agile metrics. Business metrics focus on whether the solution is meeting the market need, and agile metrics measure aspects of the development process. A program's business metrics should be rooted in its roadmap. For each initiative on the roadmap, include several key performance indicators (KPIs) that map to the program's goals. In addition, include success criteria for each product  requirement  such as adoption rate by end-users or percentage of code covered by automated tests. These success criteria feed into the program's agile metrics. And the more teams learn, the better they can adapt and evolve.  How to use agile metrics to optimi...
1 comment
Read more

The Characteristics of a Successful Agile Coach

1. Patience An agile coach, just like any coach, needs to be patient with the people they are leading. If you want your business to be agile, then you need  everyone in your company  to fully-understand what you’re working towards, and not everyone is going to “get it” straight away. Ultimately, you’re probably going to be asked the same question a thousand different times, and you need to figure out how to keep your cool. 2. Flexibility The agile framework can’t exist without flexibility. The whole point of being “agile” in the business world, is being able to adapt to changes in your marketplace. In other words, as a coach, you’ll need to be prepared for whatever happens in your organization, and have a certain strength about you when it comes to rolling with the punches. There will be times when you face challenges that leave you scratching your head and wondering what to do next. However, whenever you encounter a new scenario, you need to be able to take your trie...
5 comments
Read more

Agile metric to measure agile success

#1 On-Time Delivery According to the  State of Agile survey , 58% of the respondents* said they measured the success of their agile initiatives by on-time delivery. With agile, our schedule is fixed and our scope is flexed. What does that mean for on-time? Well, time just happens, so theoretically, we are always on time. But, on-time is generally measured in context with the expectations about what will be delivered. To measure and have visibility of what is being delivered, we may look to the out-of-the box metrics of  the burndown or the burnup . For instance, in this VersionOne burndown chart you can see progress as the team heads toward an expected end date. This burnup chart, on the other hand, allows you to see the trend of getting stuff done, as well as the impact of scope changes. #2 Product Quality A total of 48% of the respondents to the survey said they measured the success of their agile initiatives through product quality. Quality is often...
1 comment
Read more