Copy rights 2013.

 Exam Eligibility  Exam Pattern  Pre requisites  Content Distribution  Tools and Techniques  Domains and Tasks for Agile Certification (PMI®-ACP) Agile Certified Practitioner

CategoryEducationPM education General PMAgile PM Experience OneBachelors 21 contact Hours from REP 2000 hrs 1500 hrs (Last 2 Years) Two High21 contact SchoolHours from REP 4000 hrs 1500 hrs (Last 2 Years) (PMI®-ACP) Agile Certified Practitioner

 No of Questions : 120  Duration : 3 hours PartPercentage Agile Tools and Techniques Agile Knowledge and Skills 50% (PMI®-ACP) Agile Certified Practitioner

Group of software development methods based on Iterative and incremental development Requirements and solutions evolve through collaboration between self-organizing, Cross-functional teams Promotes adaptive planning, evolutionary development and delivery. Time-boxed iterative approach Encourages rapid and flexible response to change It is a conceptual framework that promotes foreseen interactions throughout the development cycle. The Agile Manifesto introduced the term in (PMI®-ACP) Agile Certified Practitioner 9

In February 2001, 17 software developers met to discuss lightweight development methods. They published the Agile Manifesto for Software Development to define the approach now known as agile software development (PMI®-ACP) Agile Certified Practitioner 10

Lightweight agile software development methods evolved in the mid-1990s as a reaction against the Heavyweight waterfall-oriented methods RUPScrum, DSDM Crystal Clear, XP ASD, FDD These are now collectively referred to as agile methodologies (PMI®-ACP) Agile Certified Practitioner

Agile practices are gaining in popularity Survey Respondent 26% 74% Claim Mature Adoption Forrester Study shows 74% of respondents claim a mature adoption of agile (“How Agile is Your Organization?, April 30,2013) Agile provides a great way for software development organizations to deliver quality software in a predictable fashion Many organizations use a combination of agile and waterfall techniques depending on goals. 12

Give me all requirements, otherwise it will cost you! 13

Traditional Software Development Agile Software Development Requirements are analyzed Architecture and Design are created Requirements are implemented, tested and delivered Months (or longer) occur before usable software for customer to evaluate Requirements are translated into User Stories and become the product backlog Usable chunks (high Value Stories) of software are developed in short periods of time (sprints, iterations, etc.) Customer works with the team and reviews software regularly Priorities may shift from iteration to iteration Agile teams expect and embrace change 14

Traditional Project ManagementAgile Project Management Planning given importanceExecution given importance than planning Scope is fixed. Time and cost are derived Time and cost are fixed. Scope is derived Delivering within triple constraint is a success Delivering business value is the success of the project Scope once fixed follows change control Process and customer charged for every change Scope is flexible and change is accommodative Project manager controls the project and Controls the team Team controls the project and team is self organizing to take care of the project Documents are interim deliverables and Final product is delivered at the end of the phase Incremental product is delivered to Customer frequently (PMI®-ACP) Agile Certified Practitioner

Toll FREE : (India) (UK) (Australia) (USA) (Nigeria) THANK YOU CONTACT US