To help prepare for your PMI-ACP exam, I have provided a number of test questions based on my experience with Agile and from teaching Agile PMI-ACP certification courses. If you’re looking for more additional training and prep questions, check out the leading provider of technology training, SimpliLearn.
- Two minutes per person
- 30 minutes
- 15 minutes for a 4 week sprint, 10 minutes for a 2 week sprint
- 15 minutes only
Scrums specifies the duration of the daily stand-up or scrum meeting to 15 minutes. This ensures it is focused on dealing with project specific updates.
- Six plus or minus two
- Six plus or minus three
Scrum specifies three roles: Scrum Master, Product Owner and Team
- Comprehensive documentation
- Top down management and tooling
- Processes and tools
- Contract negotiation
The Manifesto states Individuals and Interactions over processes and tools. Remember the Manfiesto states that while there is value to the items on the right of the statement, Agile emphasizes the items on the left.
- Write a test, watch it fail, write some code, watch it pass
- All Acceptance tests must pass for a card to be considered complete
- All code that is checked in must be compiled against the master build and pass integration tests
- Tests determine the pace of development
Test Driven Development or TDD starts with writing a test and then writing code to make it pass. Overtime the developer should also refactor code to design patterns and to improve its efficiency.
- When all user stories assigned to the iteration are complete.
- When the Product Owner agrees that the goals of the iteration are met.
- When the iteration’s timebox is complete.
- When all tasks in the iteration have met the definition of done.
An iteration’s completion is determined by its timeboxed length. Once the duration of the timebox is complete the iteration is also complete. This allows the team to determine its velocity.
- The project manager
- The product owner
The team determines when a task or story is done. This criteria should include necessary testing, documentation and integration. The definition of done should be widely accessible and visible.
- Maintain a sustainable pace (a 40 hour work week)
- There is no code ownership to ensure that programmers do not have to maintain code indefinitely
- Assisting the welfare of another programmer through the use of paired programming
- Programmers should have a clear understanding of code standards to ensure their welfare.
Programmer welfare refers to maintaining a sustainable pace with no heroic efforts or overtime work to support a project deliverable.
- An enhancement made to existing functionality to address a new business requirement
- Adjustments made to existing code to improve its efficiency, structure or documentation without changing its end user functionality.
- A programming technique where two programmers work together to design a user story.
- None of the above.
As defined by Martin Fowler, a leading Agile Architect and Designer, “a change made to the internal structure of software to make it easier to understand and cheaper to modify without changing its observable behavior.”
Muda refers to the Japanese term for waste. Lean identifies seven types of waste: Transportation. Inventory, Motion, Waiting, Over-processing, Over-production, Defects and Mnemonics.
In Kanban, work in progress is minimized which leads to faster completion, better quality and greater focus on the highest priority work.
- Total Parity System
- Total Product Stories
- Toyota Production System
- Target Production System
TPS stands for Toyota Production System. Many of the techniques leveraged by Lean and Kanban were originally applied by Toyota.