Version 1.0

Take the Survey

Note: You do not have to complete the survey in one session. At the end of each set of questions you will see a "Next Questions" button. When you press this button, your answers to the questions on the current screen will be saved. If at anytime you wish to stop taking the survey and return at a later time, simply press the Stop and Finish Later button. At that point we will ask you for a username and password so we can identify you when you return to finish the survey. When you return, you should Login with your username and password so we can retrieve your existing survey and let you continue from where you left off.

Demographics

Have you previously taken this survey?
As you respond to this survey will you be thinking mostly about your:

Demographics

Does your project need to meet any regulatory requirements (ISO 9001, Sarbanes-Oxley, etc.):
Which regulatory requirements (ISO 9001, Sarbanes-Oxley, etc.):

Demographics

How long had this 'group' (as identified above) been doing agile development prior to starting this project?
Which best characterizes this project?

Demographics

About how many people were or are on the project being assessed (or your last project)?
About how many teams were on the project being assessed (or your last project)?

Demographics

What industry best describes the project being assessed?
What best describes your role on the project? (pick one)

Demographics

Does this project involve outsourced Agile development?
What is your company's name?

Demographics

What was the project's name?
Where were employees on the project located?

Demographics

What is your name?
What is your title?

Demographics

Would you like to be contacted with further information about this research?

Teamwork Questions

Teamwork Composition
  True More True than False Neither True nor False More False than True False Not Applicable
Testers and programmers are on the same team.
Team members are kept together as long as possible.
People are not on more than 2 teams
Specialists are willing to work outside their specialties to achieve team goals.
Everyone required to go from requirements to potentially shippable product is on the team.
Teams have 5-9 people on them.

Teamwork Questions

Teamwork Management
  True More True than False Neither True nor False More False than True False Not Applicable
Teams can determine who is on or off the team.
Management sets goals but doesn't tell us how to achieve them.
Team members choose which tasks to work on.
We don't need to work on non-value-adding tasks.

Teamwork Questions

Focus
  True More True than False Neither True nor False More False than True False Not Applicable
During an iteration, it feels like we're all headed toward the same goal.
Management rarely changes our priorities during an iteration.

Teamwork Questions

Communication
  True More True than False Neither True nor False More False than True False Not Applicable
We communicate mostly face-to-face.
Formal written documents are used to supplement rather than replace faster, more informal communication.
Agreements between the team and the product owner are made and perhaps documented but not enforced by signoff.
Standup meetings take less than fifteen minutes.
Teams have a stand-up meeting everyday.
Standup meetings are effective at synchronizing work.
All team members meet in person at the start of the project.

Teamwork Questions

Team Member Location
  True More True than False Neither True nor False More False than True False Not Applicable
Team members are located in the same city.
Team members are located on the same campus.
Team members are located within the same time zone.
Team members work in a shared physical environment.
Team members are located on the same floor.
Team members are located in the same building.
Team members work hours that overlap substantially.

Requirements Questions

Communication Focus
  True More True than False Neither True nor False More False than True False Not Applicable
Our product owner is available to discuss features during the iteration.
We acknowledge that not all details can be conveyed in written specifications.
The details of a feature are fleshed out in just-in-time discussions.
Written requirements are augmented with discussion.

Requirements Questions

Level of Detail
  True More True than False Neither True nor False More False than True False Not Applicable
Teams are able to start projects with incomplete requirements.
During an iteration the specific details of some features are negotiable.
Requirements are represented at different levels of detail based on how soon we expect to implement them.

Requirements Questions

Emergence
  True More True than False Neither True nor False More False than True False Not Applicable
Product owners acknowledge that sometimes features turn out to be bigger than anyone thought.
Change is a natural part of our business; we accept it and embrace it at resonable times.
Product owners can change requirements without a lot of fuss.
Development teams can request and negotiate requirements changes with product owners.

Requirements Questions

Technical Design
  True More True than False Neither True nor False More False than True False Not Applicable
Technical design occurs iteratively throughout a project.
Projects to not begin with a big, distinct technical design phase.
Technical design is a team activity rather than something performed by individuals working alone.

Planning Questions

Planning Levels
  True More True than False Neither True nor False More False than True False Not Applicable
Before the first iteration, we create an initial plan that shows an incremental release of features and update this plan during the project.
At the start of each iteration we create a plan showing the tasks that we'll work on during that iteration.

Planning Questions

Critical Variables
  True More True than False Neither True nor False More False than True False Not Applicable
One or more of scope, schedule, or resources is allowed to change during a project.
Product owners prioritize work for teams.
Product owners are willing to discuss tradeoffs between scope and schedule.

Planning Questions

Progress Tracking
  True More True than False Neither True nor False More False than True False Not Applicable
We create an update iteration burndown charts, which shows how estimated work is remaining each day.
Teams know their velocity.
Features are either complete or not; no partial credit it given.
At the end of each iteration, we create a release burndown chart, which shows how much work remains in the release.

Planning Questions

Sources of dates and estimates.
  True More True than False Neither True nor False More False than True False Not Applicable
Developers are included in the planning process in a way that they can meaningfully and appropriately affect scope and deadlines.
Estimates are created collaboratively by the people who will do the work.

Planning Questions

When do we plan?
  True More True than False Neither True nor False More False than True False Not Applicable
Effort spent on planning is spread approximately evenly throughout the project.
Upfront planning is helpful without being excessive.
Teams communicate the need to change release date or scope as soon as they are discovered.
Team members leave planning meetings knowing what needs to be done and have confidence they can meet their commitments.

Technical Practices Questions

Test-driven Development
  True More True than False Neither True nor False More False than True False Not Applicable
All production code is written using test-driven development.
Programmers always write a failing test before writting production code.

Technical Practices Questions

Pair Programming
  True More True than False Neither True nor False More False than True False Not Applicable
When someone goes on vacation we don't worry about who will cover his or her work.
Production code is written using pair-programming.
People switch pairing partners at least once a day.
We have a physical and computer infrastructure that supports pair programming.

Technical Practices Questions

Refactoring
  True More True than False Neither True nor False More False than True False Not Applicable
Any code can be refactored; no code is too dangerous to touch.
Refactoring is performed whenever needed.
Code contains little or no duplication.
There are enough automated tests that we can refactor without worrying about breaking existing functionality.

Technical Practices Questions

Continuous Integration
  True More True than False Neither True nor False More False than True False Not Applicable
Source code is stored in a configuration management system.
Unit and acceptance tests are run as part of each automated build.
The entire system is built automatically at least once per day.
Developers check in code at least once per day.

Technical Practices Questions

Coding Standards
  True More True than False Neither True nor False More False than True False Not Applicable
Coding standards are effective at helping support collective code ownership.
Coding standards are known and used by the whole team.
We have a coding standard for each language we use.

Technical Practices Questions

Collective Code Ownership
  True More True than False Neither True nor False More False than True False Not Applicable
Anyone is allowed to change any code.
There are enough automated tests that everyone feels safe changing any code without worrying about breaking existing functionality.

Quality Questions

Automated unit testing
  True More True than False Neither True nor False More False than True False Not Applicable
Running all unit tests is fast, so we run them frequently.
The entire suite of unit tests is run in an automated way.
Programmers always write automated unit tests.
All unit tests are run and pass before code is checked in.

Quality Questions

Customer acceptance tests
  True More True than False Neither True nor False More False than True False Not Applicable
Acceptance testing is automated and run at least once a day.
Product owners provide the acceptance criteria for each feature.
A feature is not complete until its acceptance tests pass.

Quality Questions

Timing
  True More True than False Neither True nor False More False than True False Not Applicable
There is no big handoff between programmers and testers either during or at the end of an iteration.
Testers are productive right from the start of each iteration.
All bugs are fixed during the iteration in which they are found.
All types of testing(performance, integration, scalability, and so on, for example) is performed each iteration.
At the end of each iteration the is little or no manual testing required.

Culture Questions

Management style
  True More True than False Neither True nor False More False than True False Not Applicable
Product owners are willing to consider delivering less than a 100% of a solution.
Developers and product owners participate equally in determining what features will be included in a given release (i.e., release planning).
Management allows team members to make the decisions that should be theirs to make.
Teams feel an appropriate amount of pressure to meet deadlines.
We don't cancel training, holiday, and vacation time when behind schedule.
We maintain a high rate of productivity without being overworked.
Product owners understand that sometimes solving 20% of the problem delivers 80% of the value.

Culture Questions

Response to stress
  True More True than False Neither True nor False More False than True False Not Applicable
When faced with a stressful situation, our initial reaction is to prioritize and explore tradeoffs.
We avoid people having to work long stretches of evenings and weekends to meet deadlines.
We rarely add people when changing scope or schedule might be better solutions.

Culture Questions

Customer involvement
  True More True than False Neither True nor False More False than True False Not Applicable
Product owners are co-located with teams.
Product owners respond to team requests in a timely manner.
Product owners and other stakeholders are consistently involved throughout the entire project.
Teams have reasonable access to their product owners.

Culture Questions

Title and salary alignment
  True More True than False Neither True nor False More False than True False Not Applicable
Bonuses, annual reviews, and compensation promote team behavior.
Titles are not significant in how team members interact with one another.

Culture Questions

Infrastructure
  True More True than False Neither True nor False More False than True False Not Applicable
Our telecom systems (phones, VOIP, video conferencing, conference calling) help us be agile.
Our software tools help us be agile.
We aren't forced to use software tools that don't help us.
Our physical environment (office space, conference rooms, access to white boards, etc.) help us be agile.

Culture Questions

People
  True More True than False Neither True nor False More False than True False Not Applicable
Team members have the appropriate skills and knowledge to do agile development.
Our ScrumMaster or project manager is good at their job.
Team members know who their ScrumMaster or project manager is.
Our default answer is 'yes' rather than 'no, it can't be done.'
Product owners are good at their job.
Team members know who their product owner is.

Knowledge-Creating Questions

Reflection
  True More True than False Neither True nor False More False than True False Not Applicable
Iteration retrospectives lead to refinements in our process.
Iteration retrospectives are attended by all team members.
Iteration reviews are attended by product owners, stakeholders, and team members who actively participate.
We hold retrospective meetings at the end of each iteration during which we evaluate how we're doing and discuss how to get better.
We get actionable feedback from our iteration review meetings.
We do iteration reviews at the end of each iteration during which we solicit feedback on the state of the software.

Knowledge-Creating Questions

Timeboxes
  True More True than False Neither True nor False More False than True False Not Applicable
At the end of iterations, we have working software that could be given to friendly first users.
All work is done in iterations of no more than 30 days.
Within our iterations work such as design, coding and testing overlay rather than being performed sequentially; this is, no mini-waterfalls.
We agree on how much testing and how much deployment must be done within the iteration.

Knowledge-Creating Questions

Team learning
  True More True than False Neither True nor False More False than True False Not Applicable
Teams exhibit courage in discussing problems.
We ask questions of each other as often as we advocate positions.
We value learning new approaches, technologies, skills and practices.
We are willing to acknowledge and adopt other options.
We share a set of common principles.

Thank you for completing the survey!

Currently you are not logged in to a Comparative Agility account. If you want to return at a later date and see your survey results or take a future survey and potentially be able to compare your future answers with the answers to this survey, you will need an account.

Here are some options:

No thanks, I don't want to associate this survey with an account. Consider my survey to be anonymous!

Btn_orange_login I already have a Comparative Agility account, and I want to login to that account and have my survey automatically associated with that account.

Btn_orange_signup I don’t have a Comparative Agility account, but I want to sign-up for one and have my survey automatically associated with that account.