Agile Project Management has become the buzzword across all the industries in today’s world. According to Gartner, Inc., IT organizations are under intense pressure to manage project resources for near-real-time changes. That’s why IT organizations are on the lookout for people trained in agile project management. Gartner predicts the demand for agile project leaders will increase by 75 percent from 2013 to 2017.

The agile approach to project management equips project teams to deliver quality results in reduced timeframes, plan for continuous improvement and to quickly respond to changing requirements.

The Scrum is an iterative and incremental agile development framework for managing projects and enables the creation of self-organizing teams specializing in breaking down complex and large scope of work in a very short period of time and involving every team member to fully realize the potential and offer superior value proposition to clients. Without a doubt it is one of the popular and leading Agile practices in the industry.

The ACI-ASM® credential recognizes your knowledge of scrum methodologies, enterprise tools, techniques, transforming the business requirements into working software and ensuring the productivity of the team. It is the ideal certification to test the candidate's ability to apply the skills and knowledge necessary in the Scrum environment.

Though I was always working in an agile process environment with better-than-peer abilities, I still felt I needed a very special Agile-focused qualification if I wanted to break the glass ceiling and accelerate my growth. The ASM® program fit in my scheme of things perfectly as there's nothing as rigorous and as global as ASM®, as this qualification is from ACI®. Today, I am viewed with a greater respect by my peers and superiors and I am able to deploy global best-practices of agile more easily at my workplace.


Benefits for Employees and Freelancers
  1. It will be your Proof of Competence and up-to-date Knowhow in Agile/Scrum.
  2. It will help you to get hired for your next challenge.
  3. It will broaden your perspective. It will help you to get more responsibilities and better career opportunities compared to your peers.
Benefits for Employers
  1. It will reduce costs by improving efficiency of your teams.
  2. It will help you to win projects with your qualified employees.
  3. It will improve employee satisfaction by encouraging them to get trained and learn.
  4. It will improve the quality of your deliverables and customer satisfaction.


Agile Scrum Master role is a very unique and broad role in Agile/ Scrum which combines all of the challenging aspects of traditional Project Management andScrum. Moreover, Scrum Master represents the customer point of view in aAgile project,to ensure maximum added value for each and every release to the customer.

We recommend you to obtain ASM® certification if you are performing one of the following roles:
  1. Business Analyst
  2. Program Manager
  3. Product Manager
  4. Team Leader
  5. Project Manager
  6. Designer
  7. Architect ..etc

Comparison of ACI ASM® with other certification bodies

Sample Certificate


  1. ACI, for all its certifications, mandates that all the applicants should have prior training in Agile practices to be eligible to apply for any ACI's certifications.
  2. You can take training from any organizations of your choice to satisfy the mandatory training requirements for the ASM® credential.
  3. You are also strongly encouraged to study the reference books suggested in the later sections of ASM® Handbook to feel confident about taking up the ASM® certification exam.


Basic concepts of the Scrum

The Scrum is an iterative and incremental agile software development framework for developing and managing software projects and application development. It was first advocated in 1986 by Hirotaka Takeuchi and IkujiroNonaka. It is called the rugby approach, as the entire process is performed by one cross-functional team across multiple overlapping phases.

The potential benefits of Scrum is realized through its tools like product backlog, sprint backlog, burn-down charts and techniques like daily meetings, sprint planning and review meetings. The team is highly motivated by challenges in developing opportunities from discussing requirements to implementing the product. Hence it represents a cultural change for organizations used to more traditional methods.

The figure below depicts a typical flow of Scrum

Scrum Flow

Scrum - Empirical Process Control Model The Scrum is based on Empiricism which states that applied knowledge is derived from experience, observation and making informed decisions on the known factors. This approach treats product development as a self-organizing process enabling Scrum teams to deliver working model software in an iterative manner to meet customer requirements.

The Three Components of an implementation of empirical process control are

Transparency: Those aspects of the process that affect the outcome must be visible to those controlling the process

Inspection: The various aspects of the process must be inspected frequently enough that unacceptable variances in the process can be detected.

Adaptation: The process or the material being processed must be adjusted if one or more aspects of the process are outside acceptable limits and the resulting product will be unacceptable.

Scrum Roles

There are three fundamental roles in the Scrum method of agile software development. These are also referred to as Core roles.

  1. Product Owner
  2. Team
  3. Scrum Master

The Product Owner is accountable for ensuring the team delivers value to the business and is the voice of the customer.The Team consists of a group ranging between 7-9 individuals with cross functional skills and is responsible for the delivery of potentially shippable product increments.

The Scrum Master is the buffer between the team and any distracting influences and he is responsible for removing the impediments to the team in their task of the deliverables. He is also responsible for defining and facilitating the process and facilitates the team to improve.

He is often referred to as the servant-leader.Scrum supports the core roles and a range of ancillary roles. The core roles are committed to the project and directly involved in building the product.

Ancillary roles are outside the Scrum and have no formal role in the Scrum process however they too are involved in the overall enterprise environments. They could be:

  1. Project Manager - Responsible for the project's success
  2. Stakeholders - Responsible for enabling the project and justify the project
  3. Project Board - Accountable for the project where issues are outside of the Scrum Team

Scrum Structure

The Scrum structures product development in cycles of work known as Sprints. A Sprint is the basic unit of development in Scrum and is of a specific fixed duration, which cannot be extended whether the work is completed or not. This is called 'Timboxed' effort.

A typical Sprint is 1-4 weeks long and takes place one after another(Sprint follows Sprint). At the beginning of each Sprint, a cross-functional team selects items from a prioritized list of requirements, andcommits to complete them by the end of the Sprint; during the Sprint, the deliverable does not change.

Each work day, the team gathers briefly to report to each other on progress, and update simple charts that orient them to the work remaining. At the end of the Sprint, the team demonstrates what they have built, and gets feedback which can then be incorporated in the next Sprint. Scrum emphasizes producing working product at the end of the Sprint is really “done”; in the case of software, this means code that is fully tested and potentially shippable.

Scrum adopts the policy of “inspect and adapt” where for a unit of development the learning and experience is improved by inspecting both the resulting product and the efficacy of the existing processes and aligning them with the product goals and practices.


The Scrum Team consists of a Product Owner, th eDevelopment Team, and a ScrumMaster. Scrum Teams are self-organizing and cross-functional. Self-organizing teams choose how best to accomplish their work, rather than being directed by others outside the team. Cross - functional teams have all competencies needed to accomplish the work without depending on others not part of the team. The team model in Scrum is designed to optimize flexibility, creativity, and productivity.

ScrumTeams deliver products iteratively and incrementally, maximizing opportunities for feedback. Incremental deliveries of “Done” product ensure a potentially useful version of working product is always available.

The Product Owner

The Product Owner is responsible for maximizing the value of the product and the work of the Development Team. How this is done may vary widely across organizations, Scrum Teams, and individuals.

The Product Owner is the sole person responsible for managing the Product Backlog. Product Backlog management includes:

  1. Clearly expressing Product Backlog items;
  2. Ordering the items in the Product Backlog to best achieve goals and missions;
  3. Optimizing the value of the work the Development Team performs;
  4. Ensuring that the Product Backlog is visible, transparent, and clear to all, and how what the Scrum Team will work on next; and,
  5. Ensuring the Development Team understands items in the Product Backlog to the level needed.

The Development Team

The Development Team consists of professionals who do the work of delivering a potentially releasable Increment of “Done” product at the end of each Sprint. Only members of the Development Team create the Increment.

Development Teams are structured and empowered by the organization to organize and manage their own work. The resulting synergy optimizes the Development Team’s overall efficiency and effectiveness.

Development Teams have the following characteristics:
  1. They are self-organizing. No one(not even the Scrum Master) tells the Development Team how to turn Product Backlog into Increments of potentially releasable functionality;
  2. Development Teams are cross-functional, with all of the skills as a team necessary to create a product Increment;

The Scrum Master

The Scrum Master is responsible for ensuring Scrum is understood and enacted. Scrum Masters do t his by ensuring that the Scrum Team adheres to Scrum theory, practices, and rules.

The Scrum Master is a servant-leader for the Scrum Team. The Scrum Master helps those outside the Scrum Team understand which of their interactions with the Scrum Team are helpful and which aren’t. The Scrum Master helps everyone change these interactions to maximize the value created by the Scrum Team.

Scrum Events

Scrum prescribes four formal events for inspection and adaptation,

  1. Sprint Planning
  2. Daily Scrum
  3. Sprint Review
  4. Sprint Retrospective

Prescribed events are used in Scrum to create regularity and to minimize the need for meetings not defined in Scrum. All events are time-boxed events, such that every event has a maximum duration. Once a Sprint begins, its duration is fixed and cannot be shortened or lengthened. The remaining events may end whenever the purpose of the event is achieved; ensuring an appropriate amount of time is spent without allowing waste in the process.

Other than the Sprint itself, which is a container for all other events, each event in Scrum is a formal opportunity to inspect and adapt something. These events are specifically designed to enable critical transparency and inspection. Failure to include any of these events results in reduced transparency and is a lost opportunity to inspect and adapt.

The Sprint

The heart of Scrum is a Sprint, a time-box of one month or less during which a “Done”, useable, and potentially releasable product Increment is created. Sprints best have consistent durations throughout a development effort. A new Sprint starts immediately after the conclusion of the previous Sprint.

Sprints contain and consist of the Sprint Planning, Daily Scrums, the development work, the Sprint Review, and the Sprint Retrospective. During the Sprint:

  1. No changes are made that would endanger the Sprint Goal;
  2. Quality goals do not decrease; and,
  3. Scope may be clarified and re-negotiated between the Product Owner and Development Team as more is learned.

Sprint Planning

The work to be performed in the Sprint is planned at the Sprint Planning. This plan is created by the collaborative work of the entire Scrum Team.

Sprint Planning is time-boxed to a maximum of eight hours for a one-month Sprint. For shorter Sprints, the event is usually shorter. The Scrum Master ensures that the event takes place and that attendants understand its purpose. The Scrum Master teaches the Scrum Team to keep it within the time-box.

Sprint Planning answers the following:
  1. What can be delivered in the Increment resulting from the upcoming Sprint?
  2. How will the work needed to deliver the Increment be achieved?

By the end of the Sprint Planning, the Development Team should be able to explain to the Product Owner and ScrumMaster how it intends to work as a self-organizing team to accomplish the Sprint Goal and create the anticipated Increment.

Sprint Goal

The Sprint Goal is an objective set for the Sprint that can be met through the implementation of Product Backlog. It provides guidance to the Development Team on why it is building the Increment. It is created during the Sprint Planning meeting. The Sprint Goal gives the Development Team some flexibility regarding the functionality implemented within the Sprint. The selected Product Backlog items deliver one coherent function, which can be the Sprint Goal. The Sprint Goal can be any other coherence that causes the Development Team to work together rather than on separate initiatives.

Daily Scrum

The Daily Scrum is a15-minute time-boxed event for the Development Team to synchronize activities and create a plan for the next 24hours.This is done by inspecting the work since the last Daily Scrum and forecasting the work that could be done before the next one. The Daily Scrum is held at the same time and place each day to reduce complexity. During the meeting, the Development Team members explain:

  1. What did I do yesterday that helped the Development Team meet the Sprint Goal?
  2. What will I do today to help the Development Team meet the Sprint Goal?
  3. Do I see any impediment that prevents me or the Development Team from meeting the Sprint Goal. Daily Scrums improve communications, eliminate other meetings, identify impediments to development for removal, highlight and promote quick decision-making, and improve the Development Team’s level of knowledge. This is a key inspect and adapt meeting.

Sprint Review

A Sprint Review is held at the end of the Sprint to inspect the Increment and adapt the Product Backlog if needed. During the Sprint Review, the Scrum Team and stakeholders collaborate about what was done in the Sprint. Based on that and any changes to the Product Backlog during the Sprint, attendees collaborate on the next things that could be done to optimize value. This is an informal meeting, not a status meeting, and the presentation of the increment is intended to elicit feedback and foster collaboration.

This is a four-hour time-boxed meeting for one-month Sprints. For shorter Sprints, the event is usually shorter. The ScrumMaster ensures that the event takes place and that attendants understand its purpose. The ScrumMaster teaches all to keep it within the time-box.

The Sprint Reviewincludesthe followingelements:
  1. Attendees in clued the Scrum Team and key stake holders invited by the Product Owner;
  2. The Product Owner explains what Product Backlog items have been “Done” and what has not been “Done”;
  3. The Development Team discusses what went well during the Sprint, what problems it ran into, and how those problems were solved;
  4. The Development Team demonstrates the work that it has “Done” and answers questions about the Increment;
  5. The Product Owner discusses the Product Backlog as it stands. He or she projects likely completion dates based on progress to date (if needed);
  6. The entire group collaborates on what to do next, so that the Sprint Review provides valuable input to subsequent Sprint Planning;
  7. Review of how the market place or potential use of the product might have changed what is the most valuable thing to do next; and,
  8. Review of the timeline, budget, potential capabilities, and market place for the next anticipated release of the product.

The result of the Sprint Review is a revised Product Backlog that defines the probable Product Backlog items for the next Sprint. The Product Backlog may also be adjusted overall to meet new opportunities.

Sprint Retrospective

The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to been acted during the next Sprint.

The Sprint Retrospective occurs after the Sprint Review and prior to the next Sprint Planning. This is a three-hour time-boxed meeting for one-month Sprints. For shorter Sprints, the event is usually shorter. The Scrum Master ensures that the event takes place and that attendants understand its purpose. The Scrum Master teaches all to keep it within the time-box. The Scrum Master participates as a peer team member in the meeting from the accountability over the Scrum process.

The purpose of the Sprint Retrospectiveis to:
  1. In spect how the last Sprint went with regards to people, relationships, process, and tools;
  2. Identify and order the major items that went well and potential improvements; and,
  3. Create a plan for implementing improvements to the way the Scrum Team does its work.

Scrum Artifacts

Scrum’s artifacts represent work or value to provide transparency and opportunities for inspection and adaptation. Artifacts defined by Scrum are specifically designed to maximize transparency of key information so that everybody has the same understanding of the artifact.

Product Backlog

The Product Backlog is an ordered list of ever thing that might be needed in the product and is the single source of requirements for any changes to be made to the product. The Product Owner is responsible for the Product Backlog, including its content, availability, and ordering.

A Product Backlog is never complete. The earliest development of it only laysout the initially known and best - understood requirements. The Product Backlog evolvesas the product and the environment in which it will be used evolves. The Product Backlog is dynamic; it constantly change stoidentify what the product needs to be appropriate, competitive, and useful. As long as a product exists, its Product Backlog also exists.

The Product Backlog lists all features, functions, requirements, enhancements, and fixes that constitute the changes to be made to the product in future releases. Product Backlog items have the attributes of a description, order, estimate and value.

Sprint Backlog

The Sprint Backlog is the set of Product Back log items selected for the Sprint, plus a plan for delivering the product Incrementand realizing the Sprint Goal.The Sprint Backlog is a forecast by the Development Team a bout what functionality will be in the next Increment and the work needed to deliver that functionality in to a “Done” Increment.

The Sprint Back log makes visible all of the work that the Development Team identifies as necessary to meet the Sprint Goal.

The Sprint Backlog is a plan with enough detail that changes in progress can be under stood in the Daily Scrum. The Development Team modifies the Sprint Back log throughout the Sprint, and the Sprint Back log emerges during the Sprint. This emergence occurs as the Development Team works through the plan and lears more about the work needed to achieve the Sprint Goal.

Definition of “Done”

When a Product Back log item or an Increment is described as “Done”, everyone must understand what “Done” means. Although this varies significantly per Scrum Team, members must have a shared understanding of what it means for work to be complete, to ensure transparency. This is the definition of “Done” for the Scrum Team and is used to assess when work is complete on the product Increment.

The same definition guides the Development Team in knowing how many Product Back log items it can select during a Sprint Planning. The purpose of each Sprint is to deliver Increments of potentially releasable functionality that adhere to the Scrum Team’s current definition of “Done.”

As Scrum Teams mature, it is expected that their definition so f “Done” will expand to include more stringent criteria for higher quality. Anyone product or system should have a definition of “Done” that is a standard for any work done on it.


1. Which of the following is NOT an Agile methodology
  1. Scrum
  2. Crystal
  3. Extreme Programming
  4. Prototyping

2. Which of the following is a 'TRUE' statement
  1. Extreme Programming is usually a set of technical practices for software development
  2. Scrum and Extreme Programming are synonymous
  3. Product Owner is a 'servant leader' who helps the rest of the team to follow the process
  4. Scrum Master does not help the team in removing obstacles

3. Each Sprint begins with a
  1. Manager-Team meeting
  2. Scrum meeting
  3. Kickoff meeting
  4. Business requirement meeting

4. How often do Scrum Teams meet
  1. Daily
  2. Weekly
  3. Project meetingsscheduled by the Project Manager
  4. Flexible

5. Conduct a Sprint meeting at the end of Sprint is
  1. Scrum rule
  2. Scrum technique
  3. Scrum methodology
  4. Generallyaccepted Scrum practice

6. Duration of a Sprint can be
  1. Extended
  2. Extended based on changing requirements
  3. Extended upon the discretion of Scrum Master
  4. Never extended

7. A typical Scrum has mandatory artifacts numbering
  1. 2
  2. 3
  3. 4
  4. Can be added as per requirement

8. Burndown Graph is a
  1. A trend of work accomplished across a time in Sprint
  2. A trend of work remaining across a time in Sprint
  3. A Sprint Plan to measure progress
  4. A Graph to assess the workload of each resource

9. Scrum was first developed by
  1. James Gosling
  2. Robert Pressman
  3. Hirotaka Takeuchi
  4. Kaizen

10. During a Sprint
  1. Sprint Backlog can be updated according to changing requirements
  2. Sprint Backlog cannot be updated according to changing requirements
  3. Sprint Backlog can be updated by discretion of Scrum Master
  4. Sprint Backlog cannot be updated by discretion of Scrum Master


According to IDC, 63% of Hiring Managers believe certified individuals are more productive than their non-certified counterparts. Get Certified. Get Ahead.

Get certified as "Accredited Agile Practitioner ASM" for 199$ Now!


I found your web site after checking out USD 2000 price from another Scrum certification provider for training and 500$ for certification. That is too much for me to personally pay for. I am interested in making a certification program from your Agile Certification Institute for ScrumMaster. However, I don't have much background and project experience with Agile/Scrum. What is your suggestion?

At this point in time, ACI® does not impose a policy that you have to be trained from any expensive training providers to appear for our certifications. You can get training on Agile concepts from our website links and also the Master Standards which are provided to you once you register for the exam. Almost 40% of our certificants appear for certifications without any additional training (other than our website links and the Master Standards made available once you register).

How are the success rates of Agile certification programs?

The first time Success rate of Accredited Agile Practitioner (AAP®) Certification Program is 80%, whereas the success rates of Accredited ScrumMaster (ASM®) Certification is 82%. For Accredited Product Owner (APO®) Certification and Accredited SAFe Agile Practitioner (ASAP®) Certification Programs are 65%. However, most candidates seem to clear the certification in their second attempt, thereby incurring no additional expenses (All our certification programs provide two attempts for a single registration towards any certification)

Can you please provide more insights about the structure of the questions of your certification programs?

The exam questions contains of a total of 75 questions to be answered in 90 minutes. The questions are based on the Master Standards approved by Agile Professional Certification Council (APCC) with a 50:50 focus on the theoretical aspects as well as practical challenges of working in an agile setting.

How soon after the registration, will I receive access to take the examination?

After you register for the exam, you have to choose a slot which is preferable for you. We provide 24 slots in a day and they are available all 365 days in a year. The remote proctoring is done via webcam (so your computer MUST have a working webcam to take up this certification). The exam software locks your screen and hence you cannot change your browser. Also you will not be allowed to move away from the computer screen during the exam. Any such violations will result in forfeiture of your attempt at the exam and you will have to take a second attempt.

How soon after the completion of my examination, will I receive my Certification and Test Results?

It is a matter of a few seconds. Your answers are processed and evaluated real-time and you will receive your test results as soon as you submit the answers of your Agile Certification Examination. However to receive the certification, you have to clear all the three levels- Written Assessment, Submission of a Thesis (600 - 900 words) and a peer / managed feedback.

Can you let me know the procedure for the examination and details of written assessment?

Before you take the examination, as part of registration you are required to upload one of the photo ID's recommended by APCC (Includes a passport, a valid driving license of your country or any other government issued photo ID). Your ID will be verified against you personally via webcam before the test lock is released on your appointed registration time so as to ensure the test takes is the person whose ID is presented. We provide 24 slots in a day and they are available all 365 days in a year. This means pretty much you can take the exam anytime you want in a year. Our proctoring team works from three different countries so as to enable 24x7 coverage of the test taking. The registration is valid for a period of one year. The remote proctoring is done via webcam (so your computer MUST have a working webcam to take up this certification). The exam software locks your screen and hence you cannot change your browser or search online or use your browser for any purpose other than taking test during this period. Also you will not be allowed to move away from the computer screen during the exam. Any such violations are treated with seriousness and you will become ineligible to continue the certification exam. You will have to take up the exam after re-scheduling and this shall be treated as a second attempt.

Can you let me know more details of Thesis submission?

The thesis to be submitted should be between 600 words and 900 words (Roughly about one A4 page equivalent). The topic can be chosen by the candidate. Several topics and samples of previous thesis submissions are provided to candidate after they clear the assessment test. Most candidates have no difficulty clearing the Thesis level.

Can you let me know more details of peer/manager submission?

Once you submit the thesis, you will have to get recommendations from three members (either peers or managers) recommending this credential be bestowed upon you. Each of the referee has to fill an online recommendation from which consists of five (5) questions on which he will be rating on a scale of 1-10 (1 is low and 10 is highest). All these recommenders must possess a valid corporate e-mail ID (Any exceptions need approval from APCC). You will have to get an aggregate of 50% in all the recommendations to obtain the ACI credential. In case, you do not get the required rating, you can modify the reference providers and re-submit to a new set of recommenders. Our past records indicate no one had difficulty clearing this final round of assessment.

What is the validity of the registration?

You must complete all the requirements of the assessment within one year from the date of registration. If you cannot complete all the formalities of the assessment, you will automatically lose your registration and have to register.

I have received your global credential for Agile Certification recently. Is there any validity to my certificate? Also, should I pay any annual membership fees?

Once you are certified by ACI®, the certification is valid for 4 years. Every 4 years you have receive 45 knowledge points (KPs) to renew your certification. The Master Standards on Agile undergo changes every few years and we want all our certificants to update their knowledge every 4 years. However, you do NOT need to write the exam again. One knowledge point is approximately equal to one hour of class room instruction or one hour of effort on reading a relevant text book etc. You will have to pay a fee of 20$ every four years to renew your credential and maintain your licence details in our certified agile Practioners database. However, most of this information is available in "My ACI" once you get certified. Most of the relevant books are available as e-copies to be read online in "My ACI®" and these count towards earning KPs.

Will you help me get a job?

ACI® does not act like a placement agency and we do not directly provide jobs to any certificants. However, "Planet ACI® " provides a networking platform for Job providers from various companies all around the planet to post relevant jobs.

While I am making examination if I lose my Internet connectivity due to some technical issues, do I have to pay again to access the certification examination?

No problem at all. If this happens please inform us per e-mail and we will reactive your examination access code free of charge.

I just passed one of your certification programs. What kind of certificate do I receive?

As soon as you complete all the requirements of the certification, you will receive a PDF certificate which is printable if you wish (as it is generated with high quality). In addition, you will also receive your paper based certificate by regular mail within 3 months of clearing all the certification requirements. Please keep in mind that our paper certifications are processed in our back offices located in Singapore, India and Qatar and will contain metal objects (lapel pins) hence you will have a long lead time of 3 months to clear the customs requirements of your country. However, our database will reflect your certificate authenticity from the instant you clear all the requirements and you can use that in your CV.

I am considering registration for your Certification program. However, I have never possessed such a certification and I just would like to understand how such a certification looks like?

You can see a low resolution and miniaturized copy of the certificate in the respective section of the programs by selecting the respecting program links and navigating.

What is the difference between the certifications provided by Agile Certification Institute and other organizations?

According to our market analysis our programs cost less than 1/5 of the lowest cost of other online Scrum certification programs with better brand in the market. Moreover, together with the trust of our thousands of certificants we have brought a modern and friendly approach into the field of online Agile / Scrum certification programs which doesn't mandate practitioners like you to receive expensive classroom trainings before you prove and certify your competence in Agile/Scrum.

Why is your cost lower than others?

We use the latest technology in certification test taking based on Remote Proctoring and Screen Locking facilities in addition to large scale certification operations which brings down our cost of operations. We pass on some of these advantages to you, our certifications takers.

Are Scrum certifications valid in Europe and in Asia?

Yes. Certifications we issue are worldwide valid including in Europe and in Asia. Our certifications are valid and recognized in more than 120 countries around the world.

Will I get reimbursement for this certification from my organization?

ACI provides you with a detailed invoice. This coupled with successful completion of a certification from ACI provides you with reimbursement in most organizations around the planet. In case, you are not successful in claiming the reimbursement, you could alert us post your successful certification through "My ACI". Our global support team will then work with the leaders of your organization to enable reimbursement.

Do I receive PDU credits for ACI courses?

Yes. Please follow PMI's procedure. Our KPs are similar to those of PMI's PDUs.

Will I get a promotion by taking up your certification?

In most organizations, this counts towards continuing education and should enable you to get recognition and improve the chances of your promotion but keep in mind that this cannot be guaranteed by ACI®. Based on a survey of more than 1000 certificants in the past, we have seen an average of 3000% ROI on their investment on ACI certifications.

I am going to register for an agile certification program. Can I make the payment by using my credit issued from a Scotland bank?

Yes. Our trusted payment partner accepts all major credit cards issued from all banks around the world including the banks from Scotland.