Capgemini Agile Framework

123456789101112131415
Across
  1. 2. consists of improving the internal structure of an existing source code, while preserving its external behavior
  2. 4. event that generally signifies the closing of a sprint also a forum to demonstrate the work that was completed within the iteration
  3. 6. a prioritized and estimated list of all outstanding product/project requirements, features, defects and other work items
  4. 8. a measure of work that can be completed, as per the definition of Done, by development team in a single iteration. It is used for capacity planning
  5. 9. Often abbreviated as XP, it is a popular example of a lightweight, Agile software development method.
  6. 12. More a technique than an actual development methodology, test driven development, often abbreviated as
  7. 13. helps the entire team to learn and apply CAF to achieve business value. He does whatever is in his power to help the Team and Product Owner to be successful
  8. 15. A Group wide agile framework with best practices and guidance adapted from industry leading frameworks such as Scrum/XP, combined with best practices that Capgemini leveraged over its four decades plus experience, in delivering complex business solutions through high quality software to our customers.
Down
  1. 1. Practice where two developers work together on a single computer to write the code needed to develop a backlog item into working software
  2. 3. A time-box of one month or less during which a “Done”, useable, and potentially releasable product Increment is created
  3. 5. a track where Product Backlog Items (PBIs) are converted into potentially shippable increment (production ready release of working software) iteratively and incrementally using 2 to 4 weeks iteration cycles.
  4. 7. part of the Lifecycle is used for laying a firm foundation for the project to begin. Here the team understands the business value to be delivered.
  5. 9. user stories whose scope is so large as to make them difficult to complete in a single iteration or accurately estimate the level of effort to deliver.
  6. 10. The goal of the meeting is to develop a plan that the team will use to apply lessons learned going forward.
  7. 11. the single custodian of the Product Backlog.
  8. 14. A test performed by the developer to verify and validate the code that the developer completed is fit for use.