Software-IT Survey

Software / IT Development Survey

(Takes approximately 10 minutes to complete)

The purpose of this survey is to understand the needs and challenges of the software and IT development industry. Your results will be kept confidential.

In return for completing the survey, you will be provided a complimentary summary of the results.

Also, shortly after the results are distributed, all respondents will be invited to a complimentary one-hour “Typical Solutions” live session where we will share the typical practices organizations perform to address these issues. Thank you.

Survey

Name
First Last
Email address (if you would like receive the summary report and be invited to the debrief session)
1. Does your organization use a defined methodology, such as Agile, Waterfall, a hybrid approach, or “We just code”
- Agile (incremental development and release)
- Waterfall (development with sequential phases)
- A hybrid development approach
- Not much defined -- We have a few gates defined and then just do work
- We just code
2. What are your typical project actual results? Select an option within each of the High-, Medium- and Low-impact categories below
High-impact to the project/organization
Medium-impact to the project/organization
Low-impact to the project/organization
Other (details)
3. For the outcomes listed above, identify some of the reasons that lead to those outcomes?
a. Challenges with: Eliciting, defining and managing product requirements (often called user requirements, epics, user stories, or features)?
Examples: We have no requirements, but we need some. Our backlog is a disaster. We only have a list of ambiguous one-liners.
- Yes - we have this issue
- No - our requirements are good
- Each project is hit or miss
Comments?
b. Challenges with: Planning/estimating/meeting commitments?
Examples: All estimates are just a guess. We are usually overcommitted and ask for forgiveness when we are behind. We don't track where we are as a project and our status graphs (e.g., burn-down charts or MS Project data) are inaccurate.
- Yes - we have this issue
- No - our planning and estimation are good
- Each project is hit or miss
Comments?
c. Challenges with: Defining “done” so a team knows what is complete and when work is ready to be delivered?
Example: There are many forgotten tasks that are discovered very late in the project, or after release to the customer.
- Yes - we have this issue
- No - "done" is solid
- Each project is hit or miss
Comments?
d. Challenges with: Code quality and rework, or numerous defects released to the customer?
Example: Software development can get stuck in testing for a long time because of the large number of defects found during test. Customers are not happy with our software when we release it.
- Yes - we have this issue
- No - very few defects are released
- Each project is hit or miss
Comments?
e. Challenges with: Team discipline to follow a routine process?
Example: Under duress, we abandon all good practices (e.g., requirements, estimation, design and testing).
- Yes - we have this issue
- No - the process for developing and managing IT solutions/software is effective and followed
- Each project is hit or miss
Comments?
f. Challenges with: Your management’s understanding, involvement and support of the process you use to develop software?
Examples: Management commits dates to the customer and skips estimation, or insists on delivery before testing is done, or changes the project scope without an evaluation of the impact.
- Yes - we have this issue
- No - management is onboard and leads
- Some managers understand, some do not
Comments?
g. Challenges with: integrating your development approach with other frameworks, such as Kanban, PMBOK, CMMI and ISO?
Examples: a) Published frameworks, such as ISO9001, are treated as additional busywork that our ISO person does. b) Published frameworks are integrated into our normal workflow, so they get performed automatically as work is done.
- Yes - we have this issue
- No - the adoption of published standards is integrated with how we work
- Hit and miss - some practices are integrated; others are an afterthought
Comments?
Other challenges (not listed above)?
h. Does your team routinely improve its project management and engineering practices?
Examples: No time allocated, no motivation, we get used to status quo.
- Yes - we consistently improve
- No - we really don't focus on this -- people do whatever they think is best
- Kind of - we try, but new practices don't stay around long
- Hit and miss - it depends on what the boss wants this month, or the last crises that got our attention
Comments?
i. If there was a custom webinar that addressed your challenges, would you attend if it was:
- 2 hours in length
- 3 hours in length
- 4 hours in length
- I would not attend — We are used to our problems!
Thanks for your input.

Software / IT Development Survey

Survey

2. What are your typical project actual results? Select an option within each of the High-, Medium- and Low-impact categories below

3. For the outcomes listed above, identify some of the reasons that lead to those outcomes?

Thanks for your input.