Welcome to your AMI4Teams E-Mail Adresse Name I agree that my personal data stated above will be used to contact me with the results of the AMI4Teams Agile Team Sprint or Iteration Does the team act in a transparent way, so that everyone who is interested can see progress, activities and impediments?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation Does the team appear and act as a "team" and not with a individual "I'm done!" mentality?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation Does the team decide alone and independently how to convert backlog items into working solutions?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation Is the customer/user of the product well known and/or even involved by the team?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation Is the team actively contributing to the backlog refinement (e.g. giving input, writing stories, adding details, asking questions, making suggestions)?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation Does the team have a "problem-solving" attitude (in contradiction to a "tell-us-what-to-do")?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation Is the team used to ask "why" questions; especially on the refinement of backlog items?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation Does the team share experiences and knowledge across other teams and the organization?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation Does the team plan and prioritize their work in order to achieve high customer (business/user) value?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation Is the development, prioritization, and refinement of backlog items well facilitated?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation 1 out of 7 Are backlog items (e. g. user stories, tickets, bug-fixing, features) clearly identified for upcoming iterations and/or the targeted minimal viable product (MVP).Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation Are the backlog items clear and understandable to all team members?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation Is the team velocity known and used in plannings?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation Does the team use techniques to achieve technical excellence, such as Extreme Programming (continuous refactoring, pair programming, Test Driven Development, …)?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation Does the team apply continuous improvement activities (like retrospectives) and do they act based on these outcomes to improve?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation Does the team work against iteration goals?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation Has the team developed an understanding of self responsiblity and self-organisation and acts accordingly?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation Does the team align on acceptance criteria to their work (e.g. to backlog items, to user stories, tasks) and does it implement and test according to these criterias?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation Does the team contribute to backlog refinement with max. 10% of its time?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation Does the team consider an iteration planning (e. g. sprint planning) and structure its activities respectively (e. g. work estimation: small, medium, large)?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation 2 out of 7 Is a testing approach defined for all necessary layers (incl. unit tests, integration tests, individual developer tests, regression tests, end-to-end tests and tests covering non-functional requirements)?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation Does the team have test scenarios in place to fully test the implementation of each backlog item (at least one test case for each item)?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation Are regression tests automated on all relevant levels (e.g. User Interface, APIs etc.)?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation Are automated tests integrated in the activitites of the team?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation Are tests written for each technical layer and for each test level?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation Are integration tests in place?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation Are deployments automated and failure resistent (e. g. rollback is possible)?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation Are deployements of depending components synchronized?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation Is test data available and is it possible to easily reproduce it?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation How many weeks are there in average beetween releases (production/market)?Deselect Answerno release until everything is donereleasing once a yearreleasing after aprox. 3 monthsrelease after approx. 4 to 8 weeksreleasing approx. each 2 weeks 3 out of 7 Is the (solution) architecture documented in an easy, understandable, and sufficient way?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation Are developers, unit, and regression tests a standard approach and part of continous delivery?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation Are quality improvements implemented by the team effect the overal quality?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation Reflects the team quality topics and plans improvements for each iteration (e.g. using the retrospective event accordingly)?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation Is the team actively reducing technical debt?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation Does the team have agreed quality standards and is building quality into the increment(s)?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation Does the team formulate, apply, and adapt a Definition of Ready (DoR) for their iteration work?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation Does the team formulate, apply, and adapt a Definition of Done (DoD) for their iteration work?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation Is a quality backlog, which covers improvements, in place and used?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation Does the team demo what has been built in regular cadence?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation 4 out of 7 Does the team understand the required service levels (SLA) and does the product under development cover all these requirements to bring it into operation?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation Is an aligned ticket system in place that enables to implement changes in an operational environment (including the relevant tool integration)?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation Is a concept for service monitoring and alerting in the operational environment in place?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation Does the team have a clear understanding of the overall development and integration cycle?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation Is an implementation process established that reflects changes (including documentation, definition of approval steps, agreement on it between affected parties/persons/units/etc.)?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation Does the team understand the required level of data privacy, legal requirements, and other pre-defined regulations in the operational environment and implements the product accordingly?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation Is the handover process from project delivery to operations clearly described and adhered to?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation Are necessary hardware requirements for the operational environment defined and available for operational use of the new product/increment?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation Is the required documentation for operational use of the product/increment available and up-to-date?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation Is a workflow established that separates operational changes (e. g. bug fixing, tickets) on demand (including rules for prioritization and release management.)?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation 5 out of 7 Does the team work self-organized?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation Do team members help each other to achieve the iteration goals (e. g. take over tasks outside their specialization)?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation Does an (agile) coach facilitate team events when needed?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation Does the team meet regularly and as a whole to coordinate their work and resolve impediments (e. g. each day at the same time and place)?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation Does the team hold a retrospective after each iteration and defines and plans changes to continuously improve its performance?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation Do all team members respect and trust each other?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation Is a refinement performed regularly?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation Does the team have transparency on the (overall) backlog?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation Does an event to present the resulting work (e. g. review, demo) take place at the end of each iteration?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation Has the team has all necessary skills to perform its work (self-organized and interdisciplinary)?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation 6 out of 7 Does each iteration have a clear goal which is visible to all team members and stakeholders?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation Do regular events take place where feedback is given in regards to the work done of the past iteration (e.g. demos, reviews)?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation Is the Team able to give an update on the progress of work at any time?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation Are the roles of the team members clearly defined and communicated also into the organization?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation Is the team well aware of changes and updates with regard to the product and its requirements?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation Is the flow of work visible on a (team) board?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation Do the team members manage dependencies and stay in-sync with each other?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation Are stakeholders/users/customers invited to relevant (team) events/meetings?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation Is there a clear understaning of the different agile roles and is it adhered to?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation Is there a clear definition of how to communicate and which tools are to be used?Deselect Answernot at allhardly meets expectationalmost meets expectationmeets expectationabove expectation 7 out of 7 Time is Up!
