POSITION: Which best describes your current position?,EXPERIENCE: How many years of work experience do you have?,DEPARTMENT SIZE: Number of IT/Systems/Development people in your organization,SECTOR: Which sector is your organization primarily in?,LOCATION: Where are you located?,AGILE EXPERIENCE: How much experience at agile software development do you personally have?,TEAM SIZE: How many IT people are/were on the project team?,CHARACTERISTICS: Which characteristics apply to the project?,,,,,,,,"PROJECT INITIATION: How long did it take for your project team to get started?  This would include initial modeling, initial release planning, obtaining initial funding, identifying initial team members, setting up the initial team environment, and so on.  This effort is often referred to as Sprint 0 (and sometimes pre-Sprint 0), Iteration 0, the Warm Up phase/sprint/iteration, or the Inception phase/sprint/iteration.  Choose the best answer.",INITIAL REQUIREMENTS: What was your team's approach to initial requirements modeling?  Check all that apply.,,,,,,,,,,INITIAL ARCHITECTURE: What was your team's approach to initial architecture modeling?  Check all that apply.,,,,,,,,,,INITIAL ESTIMATION: How did your team approach the initial estimation effort for your project?,,FUNDING STRATEGY: What approach to funding the project was taken?,INITIAL SCHEDULE: How did your team approach the initial scheduling effort for your project?,,END DATE: Does your project have a firm deadline?,,JUSTIFICATION: Did you need to justify this project to obtain funding?  Check all that apply.,,,,,,,,"VISION: We had to produce a project vision document, or something similar such as a project charter or stakeholder goals document, as part of project initiation."
Response,Response,Response,Response,Response,Response,Response,The team has daily access to stakeholders,There are many types of stakeholders,Regulatory compliance is an issue,This is a mission-critical project,We are evolving an existing legacy system,Our system accesses legacy data,Our system integrates with legacy systems/components,The team is co-located in a single room,Response,No modeling at all,High-level modeling using whiteboards and paper,High-level modeling using drawing tools,High-level modeling using modeling/CASE tools,Detailed modeling using whiteboards and paper,Detailed modeling using drawing tools,Detailed modeling using modeling/CASE tools,Initial models were provided to us,Enterprise models used as reference,Industry models used as reference,No modeling at all,High-level modeling using whiteboards and paper,High-level modeling using drawing tools,High-level modeling using modeling/CASE tools,Detailed modeling using whiteboards and paper,Detailed modeling using drawing tools,Detailed modeling using modeling/CASE tools,Initial models were provided to us,Enterprise models used as reference,Industry models used as reference,Response,Other (please specify),Response,Response,Other (please specify),Response,Other (please specify),We had to estimate the return on investment (ROI),We had to estimate the net present value (NPV),We had to show that our proposed solution was technically feasible,We had to show that our proposed solution could be supported by our operations group,We had to show that we considered commercial packages,We had to show that we considered offshoring the project,We had to show that our stakeholders agreed to the scope,Other (please specify),Response
Project Manager,10 to 20 years,11 to 50,Technology (inc. Software),Australia/NZ,1-2 years,10-Jun,,,,,,Our system accesses legacy data,Our system integrates with legacy systems/components,The team is co-located in a single room,1 week,,High-level modeling using whiteboards and paper,,,,,,,,,No modeling at all,,,,,,,,,,High-level estimate based on agile estimation technique (e.g. planning poker),,Fixed price,High-level release plan,,"Yes, we have promised an end date but it may change",,,,,,,,,,Yes
Agile Team Member,Less than 2 years,11 to 50,Financial,North America,1-2 years,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Product Owner,2 to 5 years,1 to 10,Other,North America,< 1 year,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
IT Manager,20+ years,501 to 1000,Financial,Europe,5-10 years,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Agile Team Member,Less than 2 years,1 to 10,IT Consulting,Asia,1-2 years,10-Jun,,,,,,,,,2 weeks,,,,,Detailed modeling using whiteboards and paper,,,,,,,,,,,,,Initial models were provided to us,,,High-level estimate based on a reasonable guess of experience person(s),,Fixed price,No initial project schedule,,"Yes, the end date is firm due to business need",,,,,We had to show that our proposed solution could be supported by our operations group,,,,,Yes
Business Analyst,20+ years,1 to 10,e-Commerce,Europe,3-4 years,5-Jan,,There are many types of stakeholders,,This is a mission-critical project,We are evolving an existing legacy system,Our system accesses legacy data,Our system integrates with legacy systems/components,,Don't know,,High-level modeling using whiteboards and paper,,,Detailed modeling using whiteboards and paper,Detailed modeling using drawing tools,,,,,,High-level modeling using whiteboards and paper,,,Detailed modeling using whiteboards and paper,,,,,,Detailed estimate based on traditional estimation technique,,Don't know,Detailed schedule,,"No, we are still negotiating",,We had to estimate the return on investment (ROI),We had to estimate the net present value (NPV),We had to show that our proposed solution was technically feasible,We had to show that our proposed solution could be supported by our operations group,We had to show that we considered commercial packages,We had to show that we considered offshoring the project,We had to show that our stakeholders agreed to the scope,,Don't Know
Team Lead/Scrum Master,5 to 10 years,1 to 10,Technology (inc. Software),North America,3-4 years,5-Jan,The team has daily access to stakeholders,There are many types of stakeholders,,This is a mission-critical project,,Our system accesses legacy data,Our system integrates with legacy systems/components,The team is co-located in a single room,2 weeks,,High-level modeling using whiteboards and paper,,,,,,,,,,High-level modeling using whiteboards and paper,,,,,,,,,High-level estimate based on agile estimation technique (e.g. planning poker),,Staged-gate funding,High-level release plan,,"Yes, the end date is firm due to business need",,We had to estimate the return on investment (ROI),,We had to show that our proposed solution was technically feasible,,We had to show that we considered commercial packages,We had to show that we considered offshoring the project,,,No
Architect,10 to 20 years,11 to 50,Other,North America,1-2 years,10-Jun,,There are many types of stakeholders,Regulatory compliance is an issue,This is a mission-critical project,,Our system accesses legacy data,Our system integrates with legacy systems/components,,3 weeks,,High-level modeling using whiteboards and paper,High-level modeling using drawing tools,,,,,,,,,High-level modeling using whiteboards and paper,High-level modeling using drawing tools,,,,,,Enterprise models used as reference,,High-level estimate based on a reasonable guess of experience person(s),,Staged-gate funding,High-level release plan,,"Yes, we have promised an end date but it may change",,,,,,We had to show that we considered commercial packages,,We had to show that our stakeholders agreed to the scope,,Yes
Architect,10 to 20 years,11 to 50,Technology (inc. Software),Asia,< 1 year,5-Jan,,There are many types of stakeholders,,,We are evolving an existing legacy system,,Our system integrates with legacy systems/components,,2 weeks,,High-level modeling using whiteboards and paper,,,,,,,,,,High-level modeling using whiteboards and paper,,,,,,,,,High-level estimate based on a reasonable guess of experience person(s),,Time and materials,Detailed schedule,,"No, we are still negotiating",,We had to estimate the return on investment (ROI),,We had to show that our proposed solution was technically feasible,,,,,,Yes
Team Lead/Scrum Master,10 to 20 years,1000+,Retail,North America,3-4 years,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Agile Team Member,10 to 20 years,1 to 10,IT Consulting,North America,3-4 years,5-Jan,The team has daily access to stakeholders,There are many types of stakeholders,,This is a mission-critical project,,,,,4 weeks,,High-level modeling using whiteboards and paper,,,,,,,,Industry models used as reference,,High-level modeling using whiteboards and paper,,,,,,,,Industry models used as reference,High-level estimate based on a reasonable guess of experience person(s),,We are still negotiating this,High-level release plan,,"No, we will ship when our stakeholders tell us to",,,,We had to show that our proposed solution was technically feasible,,,,,,Yes
Programmer,Less than 2 years,51 to 100,IT Consulting,Asia,< 1 year,21-50,,,,This is a mission-critical project,,,,,5-6 weeks,,,,,,Detailed modeling using drawing tools,,Initial models were provided to us,,,,,,,Detailed modeling using whiteboards and paper,,,,,,"High-level estimate based on traditional estimation technique (e.g. COCOMO II, Function Points)",,Staged-gate funding,High-level release plan,,"Yes, the end date is firm due to business need",,,,We had to show that our proposed solution was technically feasible,,,,,,Yes
Agile Team Member,10 to 20 years,51 to 100,e-Commerce,Europe,1-2 years,20-Nov,,,,,,,,,2 weeks,,,,,,,,,,,,,,,,,,,,,No initial estimate at all,,Staged-gate funding,High-level release plan,,"Yes, the end date is firm due to legislation",,,,,We had to show that our proposed solution could be supported by our operations group,,,,,No
Business Analyst,2 to 5 years,101 to 500,e-Commerce,North America,< 1 year,10-Jun,The team has daily access to stakeholders,There are many types of stakeholders,Regulatory compliance is an issue,,We are evolving an existing legacy system,,Our system integrates with legacy systems/components,,5-6 weeks,,,,High-level modeling using modeling/CASE tools,,,,,,,No modeling at all,,,,,,,,,,High-level estimate based on agile estimation technique (e.g. planning poker),,Fixed price,High-level release plan,,"Yes, the end date is firm due to legislation",,,,,,,,,,Yes
Team Lead/Scrum Master,10 to 20 years,501 to 1000,Retail,North America,5-10 years,10-Jun,The team has daily access to stakeholders,,,,,Our system accesses legacy data,Our system integrates with legacy systems/components,The team is co-located in a single room,5-6 weeks,,,High-level modeling using drawing tools,,Detailed modeling using whiteboards and paper,,,,,,,High-level modeling using whiteboards and paper,High-level modeling using drawing tools,,,,,,,,High-level estimate based on agile estimation technique (e.g. planning poker),,Staged-gate funding,High-level release plan,,"No, we will ship when our stakeholders tell us to",,,,We had to show that our proposed solution was technically feasible,,We had to show that we considered commercial packages,,We had to show that our stakeholders agreed to the scope,,Yes
Business Analyst,5 to 10 years,101 to 500,Technology (inc. Software),North America,< 1 year,10-Jun,The team has daily access to stakeholders,There are many types of stakeholders,Regulatory compliance is an issue,,,,Our system integrates with legacy systems/components,The team is co-located in a single room,> 8 weeks,,High-level modeling using whiteboards and paper,High-level modeling using drawing tools,,Detailed modeling using whiteboards and paper,,,,,,,High-level modeling using whiteboards and paper,,,,,,Initial models were provided to us,,,High-level estimate based on agile estimation technique (e.g. planning poker),,Staged-gate funding,Don't know,Release schedule keeps changing due to greater organizational changes,"No, we will ship when our stakeholders tell us to",,We had to estimate the return on investment (ROI),We had to estimate the net present value (NPV),,,,,We had to show that our stakeholders agreed to the scope,,Yes
Operations/Support,20+ years,1 to 10,Financial,North America,3-4 years,5-Jan,The team has daily access to stakeholders,,,This is a mission-critical project,,,,The team is co-located in a single room,1 week,,High-level modeling using whiteboards and paper,,,,,,,,,,High-level modeling using whiteboards and paper,,,,,,,,,No initial estimate at all,,Fixed price,High-level release plan,,"Yes, the end date is firm due to business need",,We had to estimate the return on investment (ROI),,,,,,,,No
Project Manager,10 to 20 years,101 to 500,Technology (inc. Software),Europe,1-2 years,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Team Lead/Scrum Master,5 to 10 years,11 to 50,Financial,South/Central America,1-2 years,10-Jun,,There are many types of stakeholders,,,We are evolving an existing legacy system,,Our system integrates with legacy systems/components,,> 8 weeks,,High-level modeling using whiteboards and paper,,High-level modeling using modeling/CASE tools,,,,,,,,High-level modeling using whiteboards and paper,High-level modeling using drawing tools,,,,,,,,High-level estimate based on a reasonable guess of experience person(s),,Time and materials,High-level release plan,,"Yes, we have promised an end date but it may change",,We had to estimate the return on investment (ROI),,We had to show that our proposed solution was technically feasible,,,,,,Yes
Team Lead/Scrum Master,10 to 20 years,11 to 50,Technology (inc. Software),Europe,1-2 years,5-Jan,,,,,,,Our system integrates with legacy systems/components,,> 8 weeks,,High-level modeling using whiteboards and paper,High-level modeling using drawing tools,High-level modeling using modeling/CASE tools,,,,,,,,High-level modeling using whiteboards and paper,High-level modeling using drawing tools,High-level modeling using modeling/CASE tools,,,,,,,High-level estimate based on a reasonable guess of experience person(s),,Fixed price,High-level release plan,,"Yes, we have promised an end date but it may change",,,,We had to show that our proposed solution was technically feasible,We had to show that our proposed solution could be supported by our operations group,,,We had to show that our stakeholders agreed to the scope,,Yes
Programmer,Less than 2 years,11 to 50,Financial,Asia,1-2 years,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Architect,10 to 20 years,101 to 500,Financial,North America,1-2 years,10-Jun,,,Regulatory compliance is an issue,This is a mission-critical project,We are evolving an existing legacy system,,,,Don't know,No modeling at all,,,,,,,,,,No modeling at all,,,,,,,,,,High-level estimate based on a reasonable guess of experience person(s),,We are still negotiating this,High-level release plan,,"No, we are still negotiating",,,,,,,,,This is ongoing development,No
Project Manager,5 to 10 years,101 to 500,Retail,Europe,1-2 years,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Project Manager,10 to 20 years,11 to 50,IT Consulting,Europe,5-10 years,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Programmer,2 to 5 years,101 to 500,IT Consulting,Europe,1-2 years,10-Jun,,,,,,Our system accesses legacy data,Our system integrates with legacy systems/components,The team is co-located in a single room,> 8 weeks,,High-level modeling using whiteboards and paper,,,Detailed modeling using whiteboards and paper,Detailed modeling using drawing tools,,,,,,High-level modeling using whiteboards and paper,,,Detailed modeling using whiteboards and paper,Detailed modeling using drawing tools,,,,,High-level estimate based on agile estimation technique (e.g. planning poker),,We are still negotiating this,High-level release plan,,"Yes, the end date is firm due to legislation",,,,,,,,,,Yes
Project Manager,10 to 20 years,101 to 500,Other,Europe,5-10 years,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Business Analyst,Less than 2 years,1 to 10,Other,South/Central America,< 1 year,20-Nov,The team has daily access to stakeholders,There are many types of stakeholders,,,,,,,> 8 weeks,,High-level modeling using whiteboards and paper,High-level modeling using drawing tools,,Detailed modeling using whiteboards and paper,,,,,,,High-level modeling using whiteboards and paper,,,Detailed modeling using whiteboards and paper,,,,,,Detailed estimate based on agile estimation technique,,Fixed price,High-level release plan,,"Yes, the end date is firm due to business need",,,We had to estimate the net present value (NPV),,,,,,,Yes
Team Lead/Scrum Master,5 to 10 years,1 to 10,Financial,North America,< 1 year,10-Jun,,There are many types of stakeholders,,This is a mission-critical project,,,Our system integrates with legacy systems/components,,Don't know,No modeling at all,,,,,,,,,,No modeling at all,,,,,,,,,,Detailed estimate based on traditional estimation technique,,Don't know,Detailed schedule,,"Yes, we have promised an end date but it may change",,,,,,,,,"No, the business had a ""lightbulb"" moment and decided on a new business venture.",No
Project Manager,10 to 20 years,1000+,Technology (inc. Software),Asia,1-2 years,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Architect,10 to 20 years,1000+,Technology (inc. Software),Asia,5-10 years,21-50,,,,,,Our system accesses legacy data,Our system integrates with legacy systems/components,The team is co-located in a single room,4 weeks,,High-level modeling using whiteboards and paper,,,,Detailed modeling using drawing tools,,,,Industry models used as reference,,High-level modeling using whiteboards and paper,,,,,,,,,"High-level estimate based on traditional estimation technique (e.g. COCOMO II, Function Points)",,Fixed price,High-level release plan,,"Yes, the end date is firm due to business need",,We had to estimate the return on investment (ROI),,,,,,,,Yes
Other,20+ years,101 to 500,Technology (inc. Software),North America,5-10 years,10-Jun,The team has daily access to stakeholders,,,This is a mission-critical project,We are evolving an existing legacy system,Our system accesses legacy data,Our system integrates with legacy systems/components,,< 1 week,No modeling at all,,,,,,,,,,No modeling at all,,,,,,,,,,High-level estimate based on a reasonable guess of experience person(s),,Don't know,No initial project schedule,,"No, we will ship when our stakeholders tell us to",,,,,,,We had to show that we considered offshoring the project,We had to show that our stakeholders agreed to the scope,,No
Project Manager,10 to 20 years,101 to 500,Technology (inc. Software),North America,5-10 years,21-50,The team has daily access to stakeholders,There are many types of stakeholders,,,,,,,4 weeks,,High-level modeling using whiteboards and paper,,,,,,,,,,High-level modeling using whiteboards and paper,,,,,,,,,High-level estimate based on a reasonable guess of experience person(s),,Time and materials,High-level release plan,,"Yes, the end date is firm due to business need",,We had to estimate the return on investment (ROI),,,,,,,,Yes
Architect,5 to 10 years,11 to 50,Manufacturing,North America,< 1 year,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Project Manager,2 to 5 years,1 to 10,Technology (inc. Software),Asia,> 10 years,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Architect,10 to 20 years,101 to 500,Technology (inc. Software),North America,5-10 years,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Programmer,10 to 20 years,11 to 50,Technology (inc. Software),North America,5-10 years,20-Nov,The team has daily access to stakeholders,There are many types of stakeholders,,,,,Our system integrates with legacy systems/components,,4 weeks,,High-level modeling using whiteboards and paper,,,,,,,,,,High-level modeling using whiteboards and paper,,,,,,,,,High-level estimate based on a reasonable guess of experience person(s),,Fixed price,High-level release plan,,"Yes, the end date is firm due to business need",The initial phase of the project has a hard deadline but the project will continue beyond that date.,,,We had to show that our proposed solution was technically feasible,,,,We had to show that our stakeholders agreed to the scope,,Don't Know
Agile Team Member,2 to 5 years,101 to 500,IT Consulting,South/Central America,1-2 years,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Programmer,2 to 5 years,51 to 100,e-Commerce,Asia,< 1 year,5-Jan,The team has daily access to stakeholders,,,,,,,,4 weeks,No modeling at all,,,,,,,,,,,,,,,,,Initial models were provided to us,,,No initial estimate at all,,Don't know,Don't know,,"No, we will ship when our stakeholders tell us to",,,,,,,,We had to show that our stakeholders agreed to the scope,,Don't Know
Project Manager,2 to 5 years,51 to 100,Technology (inc. Software),Australia/NZ,3-4 years,10-Jun,,There are many types of stakeholders,,,We are evolving an existing legacy system,Our system accesses legacy data,Our system integrates with legacy systems/components,,2 weeks,,High-level modeling using whiteboards and paper,High-level modeling using drawing tools,,Detailed modeling using whiteboards and paper,,,,,,,High-level modeling using whiteboards and paper,High-level modeling using drawing tools,,Detailed modeling using whiteboards and paper,,,,,,High-level estimate based on a reasonable guess of experience person(s),,Staged-gate funding,High-level release plan,,"Yes, we have promised an end date but it may change",,,,,,,,We had to show that our stakeholders agreed to the scope,,Yes
Project Manager,10 to 20 years,101 to 500,Financial,North America,1-2 years,20-Nov,,There are many types of stakeholders,Regulatory compliance is an issue,,,,Our system integrates with legacy systems/components,,4 weeks,No modeling at all,,,,,,,,,,No modeling at all,,,,,,,,,,"High-level estimate based on traditional estimation technique (e.g. COCOMO II, Function Points)",,Don't know,Detailed schedule,,"Yes, we have promised an end date but it may change",,,,,,,,We had to show that our stakeholders agreed to the scope,,No
IT Manager,5 to 10 years,501 to 1000,Financial,Europe,3-4 years,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Product Owner,10 to 20 years,101 to 500,Technology (inc. Software),North America,< 1 year,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Project Manager,10 to 20 years,11 to 50,Technology (inc. Software),North America,1-2 years,5-Jan,The team has daily access to stakeholders,There are many types of stakeholders,,This is a mission-critical project,We are evolving an existing legacy system,,,,2 weeks,,High-level modeling using whiteboards and paper,,,,,,,,,,High-level modeling using whiteboards and paper,,,,,,,,,High-level estimate based on agile estimation technique (e.g. planning poker),,Fixed price,High-level release plan,,"Yes, the end date is firm due to business need",,,,We had to show that our proposed solution was technically feasible,,,,,,No
Agile Team Member,2 to 5 years,51 to 100,Technology (inc. Software),South/Central America,< 1 year,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Agile Team Member,Less than 2 years,11 to 50,Retail,South/Central America,< 1 year,10-Jun,The team has daily access to stakeholders,,,,,,,,< 1 week,No modeling at all,,,,,,,,,,No modeling at all,,,,,,,,,,No initial estimate at all,,Fixed price,No initial project schedule,,"No, we will ship when our stakeholders tell us to",,We had to estimate the return on investment (ROI),,,,,,,,Yes
Business Analyst,10 to 20 years,101 to 500,Retail,Africa,< 1 year,20-Nov,,There are many types of stakeholders,,,,,Our system integrates with legacy systems/components,The team is co-located in a single room,Don't know,,High-level modeling using whiteboards and paper,,,,,Detailed modeling using modeling/CASE tools,,,,,High-level modeling using whiteboards and paper,,High-level modeling using modeling/CASE tools,,,,,,,High-level estimate based on a reasonable guess of experience person(s),,Time and materials,High-level release plan,,"No, we are still negotiating",,,,,,,,,,Don't Know
Team Lead/Scrum Master,10 to 20 years,101 to 500,e-Commerce,Europe,< 1 year,10-Jun,The team has daily access to stakeholders,There are many types of stakeholders,,This is a mission-critical project,We are evolving an existing legacy system,,Our system integrates with legacy systems/components,The team is co-located in a single room,< 1 week,,High-level modeling using whiteboards and paper,,High-level modeling using modeling/CASE tools,Detailed modeling using whiteboards and paper,Detailed modeling using drawing tools,,,,,,High-level modeling using whiteboards and paper,High-level modeling using drawing tools,,Detailed modeling using whiteboards and paper,Detailed modeling using drawing tools,Detailed modeling using modeling/CASE tools,,,,Detailed estimate based on agile estimation technique,,Time and materials,High-level release plan,,"No, we will ship when our stakeholders tell us to",,We had to estimate the return on investment (ROI),,,,,,We had to show that our stakeholders agreed to the scope,,Yes
Architect,10 to 20 years,11 to 50,IT Consulting,Australia/NZ,5-10 years,10-Jun,,There are many types of stakeholders,,,,Our system accesses legacy data,Our system integrates with legacy systems/components,,2 weeks,,High-level modeling using whiteboards and paper,High-level modeling using drawing tools,,,,,,,,,High-level modeling using whiteboards and paper,High-level modeling using drawing tools,,,,,,,,High-level estimate based on agile estimation technique (e.g. planning poker),,Fixed price,High-level release plan,,"Yes, we have promised an end date but it may change",budget expires == we finish,,,,,,,We had to show that our stakeholders agreed to the scope,,Yes
IT Manager,20+ years,101 to 500,Other,Europe,1-2 years,20-Nov,The team has daily access to stakeholders,There are many types of stakeholders,,,,Our system accesses legacy data,Our system integrates with legacy systems/components,The team is co-located in a single room,> 8 weeks,,High-level modeling using whiteboards and paper,,,,,,,,,,High-level modeling using whiteboards and paper,High-level modeling using drawing tools,,,,,,,,High-level estimate based on agile estimation technique (e.g. planning poker),,Staged-gate funding,High-level release plan,,"Yes, we have promised an end date but it may change",,We had to estimate the return on investment (ROI),,We had to show that our proposed solution was technically feasible,,We had to show that we considered commercial packages,,We had to show that our stakeholders agreed to the scope,,Yes
Project Manager,Less than 2 years,101 to 500,Other,North America,< 1 year,20-Nov,The team has daily access to stakeholders,There are many types of stakeholders,Regulatory compliance is an issue,,We are evolving an existing legacy system,,Our system integrates with legacy systems/components,,1 week,,High-level modeling using whiteboards and paper,,,Detailed modeling using whiteboards and paper,,,,,,,High-level modeling using whiteboards and paper,,,Detailed modeling using whiteboards and paper,,,,,,High-level estimate based on agile estimation technique (e.g. planning poker),,Don't know,High-level release plan,,"No, we will ship when our stakeholders tell us to",,We had to estimate the return on investment (ROI),,We had to show that our proposed solution was technically feasible,We had to show that our proposed solution could be supported by our operations group,,,We had to show that our stakeholders agreed to the scope,,No
Team Lead/Scrum Master,10 to 20 years,1000+,Government,North America,5-10 years,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Business Analyst,10 to 20 years,101 to 500,e-Commerce,North America,< 1 year,10-Jun,The team has daily access to stakeholders,,,This is a mission-critical project,We are evolving an existing legacy system,,Our system integrates with legacy systems/components,The team is co-located in a single room,1 week,,High-level modeling using whiteboards and paper,,,Detailed modeling using whiteboards and paper,,,,,,,High-level modeling using whiteboards and paper,,,Detailed modeling using whiteboards and paper,,,,,,"High-level estimate based on traditional estimation technique (e.g. COCOMO II, Function Points)",,We are still negotiating this,High-level release plan,,Don't know,,,,We had to show that our proposed solution was technically feasible,,,,,,Don't Know
Architect,10 to 20 years,11 to 50,Government,Europe,3-4 years,5-Jan,The team has daily access to stakeholders,There are many types of stakeholders,Regulatory compliance is an issue,,,,,,3 weeks,,,,High-level modeling using modeling/CASE tools,,,Detailed modeling using modeling/CASE tools,,,,,High-level modeling using whiteboards and paper,,High-level modeling using modeling/CASE tools,Detailed modeling using whiteboards and paper,,,,,,Detailed estimate based on a reasonable guess of experience person(s),,Fixed price,High-level release plan,,"Yes, the end date is firm due to business need",,,,We had to show that our proposed solution was technically feasible,We had to show that our proposed solution could be supported by our operations group,,,We had to show that our stakeholders agreed to the scope,,No
Agile Team Member,2 to 5 years,51 to 100,IT Consulting,Europe,1-2 years,5-Jan,The team has daily access to stakeholders,There are many types of stakeholders,,,We are evolving an existing legacy system,Our system accesses legacy data,Our system integrates with legacy systems/components,The team is co-located in a single room,4 weeks,,High-level modeling using whiteboards and paper,High-level modeling using drawing tools,,,,,,,,,High-level modeling using whiteboards and paper,High-level modeling using drawing tools,,Detailed modeling using whiteboards and paper,,,,,,High-level estimate based on a reasonable guess of experience person(s),,Time and materials,High-level release plan,,"No, we will ship when our stakeholders tell us to",,,,,,,,,We had to show a reasonable high level estimate for the must have stories,No
Other,5 to 10 years,1000+,Technology (inc. Software),North America,3-4 years,21-50,The team has daily access to stakeholders,There are many types of stakeholders,Regulatory compliance is an issue,,,Our system accesses legacy data,,,< 1 week,,,High-level modeling using drawing tools,,Detailed modeling using whiteboards and paper,,,,Enterprise models used as reference,,No modeling at all,,,,,,,,,,High-level estimate based on agile estimation technique (e.g. planning poker),,Time and materials with delivery bonus(s),High-level release plan,,"Yes, the end date is firm due to legislation",,We had to estimate the return on investment (ROI),,We had to show that our proposed solution was technically feasible,,,,We had to show that our stakeholders agreed to the scope,,Yes
Team Lead/Scrum Master,10 to 20 years,11 to 50,Technology (inc. Software),Europe,1-2 years,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Product Owner,10 to 20 years,51 to 100,Technology (inc. Software),Europe,1-2 years,10-Jun,The team has daily access to stakeholders,There are many types of stakeholders,,This is a mission-critical project,We are evolving an existing legacy system,,Our system integrates with legacy systems/components,The team is co-located in a single room,4 weeks,,High-level modeling using whiteboards and paper,,,,,,,,,,High-level modeling using whiteboards and paper,,,,,,,,,High-level estimate based on agile estimation technique (e.g. planning poker),,Don't know,High-level release plan,,"Yes, we have promised an end date but it may change",,,,,,,,,Project is needed for a strategic re-positioning in the market,No
Project Manager,10 to 20 years,101 to 500,Other,Europe,3-4 years,20-Nov,The team has daily access to stakeholders,There are many types of stakeholders,Regulatory compliance is an issue,,We are evolving an existing legacy system,Our system accesses legacy data,Our system integrates with legacy systems/components,,> 8 weeks,No modeling at all,,,,,,,,,,No modeling at all,,,,,,,,,,High-level estimate based on a reasonable guess of experience person(s),,Fixed price,Detailed schedule,,"Yes, the end date is firm due to business need",,We had to estimate the return on investment (ROI),,,,,,,,No
Programmer,20+ years,101 to 500,Other,North America,1-2 years,10-Jun,,There are many types of stakeholders,,This is a mission-critical project,We are evolving an existing legacy system,Our system accesses legacy data,Our system integrates with legacy systems/components,,4 weeks,,High-level modeling using whiteboards and paper,,,,,,,,,No modeling at all,,,,,,,,,,High-level estimate based on agile estimation technique (e.g. planning poker),,Staged-gate funding,High-level release plan,,"No, we are still negotiating",,We had to estimate the return on investment (ROI),,We had to show that our proposed solution was technically feasible,We had to show that our proposed solution could be supported by our operations group,,,We had to show that our stakeholders agreed to the scope,,Yes
QA/Test,5 to 10 years,51 to 100,IT Consulting,Asia,None,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
QA/Test,20+ years,51 to 100,e-Commerce,North America,3-4 years,5-Jan,The team has daily access to stakeholders,,,,,,,,4 weeks,No modeling at all,,,,,,,,,,No modeling at all,,,,,,,,,,High-level estimate based on a reasonable guess of experience person(s),,Fixed price,High-level release plan,,"Yes, we have promised an end date but it may change",,,,,,,,We had to show that our stakeholders agreed to the scope,,Yes
QA/Test,5 to 10 years,51 to 100,Technology (inc. Software),Asia,1-2 years,21-50,The team has daily access to stakeholders,There are many types of stakeholders,,This is a mission-critical project,We are evolving an existing legacy system,,Our system integrates with legacy systems/components,,5-6 weeks,,High-level modeling using whiteboards and paper,,,Detailed modeling using whiteboards and paper,,,,,,,High-level modeling using whiteboards and paper,High-level modeling using drawing tools,,,,,,,,"High-level estimate based on traditional estimation technique (e.g. COCOMO II, Function Points)",,Time and materials,Detailed schedule,,"Yes, the end date is firm due to business need",,We had to estimate the return on investment (ROI),We had to estimate the net present value (NPV),,,,,We had to show that our stakeholders agreed to the scope,,Yes
Team Lead/Scrum Master,5 to 10 years,51 to 100,e-Commerce,Europe,3-4 years,10-Jun,The team has daily access to stakeholders,There are many types of stakeholders,,,,,,The team is co-located in a single room,< 1 week,,High-level modeling using whiteboards and paper,,,,,,,Enterprise models used as reference,,,High-level modeling using whiteboards and paper,,,,,,,Enterprise models used as reference,,High-level estimate based on agile estimation technique (e.g. planning poker),,Time and materials,High-level release plan,,"Yes, we have promised an end date but it may change",,,,We had to show that our proposed solution was technically feasible,We had to show that our proposed solution could be supported by our operations group,,,We had to show that our stakeholders agreed to the scope,,No
Project Manager,10 to 20 years,11 to 50,Other,North America,1-2 years,10-Jun,The team has daily access to stakeholders,There are many types of stakeholders,,,We are evolving an existing legacy system,Our system accesses legacy data,Our system integrates with legacy systems/components,,2 weeks,,High-level modeling using whiteboards and paper,,,,,,,,,,High-level modeling using whiteboards and paper,,,,,,,,,High-level estimate based on agile estimation technique (e.g. planning poker),,Don't know,High-level release plan,,"No, we will ship when our stakeholders tell us to",,,,,,,,We had to show that our stakeholders agreed to the scope,,Yes
Programmer,5 to 10 years,11 to 50,Government,North America,< 1 year,10-Jun,The team has daily access to stakeholders,There are many types of stakeholders,,,We are evolving an existing legacy system,Our system accesses legacy data,Our system integrates with legacy systems/components,,4 weeks,,,High-level modeling using drawing tools,,,,,,,,No modeling at all,,,,,,,,,,Don't know,,Fixed price,Detailed schedule,,"Yes, the end date is firm due to business need",,,,,,,,We had to show that our stakeholders agreed to the scope,,No
Architect,20+ years,51 to 100,Technology (inc. Software),North America,1-2 years,21-50,,There are many types of stakeholders,,This is a mission-critical project,We are evolving an existing legacy system,Our system accesses legacy data,Our system integrates with legacy systems/components,,> 8 weeks,,High-level modeling using whiteboards and paper,,,,,,,,,No modeling at all,,,,,,,,,,High-level estimate based on a reasonable guess of experience person(s),,Fixed price,High-level release plan,,"Yes, the end date is firm due to business need",,,,,We had to show that our proposed solution could be supported by our operations group,,,We had to show that our stakeholders agreed to the scope,,Yes
IT Manager,20+ years,101 to 500,Other,Europe,1-2 years,10-Jun,The team has daily access to stakeholders,,,,We are evolving an existing legacy system,,,,3 weeks,No modeling at all,,,,,,,,,,No modeling at all,,,,,,,,,,High-level estimate based on agile estimation technique (e.g. planning poker),,Fixed price,High-level release plan,,"Yes, the end date is firm due to business need",,,,,,,,,,No
Project Manager,2 to 5 years,1 to 10,Technology (inc. Software),South/Central America,< 1 year,5-Jan,The team has daily access to stakeholders,,,,,,,,5-6 weeks,,,,,Detailed modeling using whiteboards and paper,,,,,,,,,,Detailed modeling using whiteboards and paper,,,,,,Don't know,,Fixed price,High-level release plan,,"Yes, we have promised an end date but it may change",,,,,,We had to show that we considered commercial packages,,,,Yes
Product Owner,10 to 20 years,501 to 1000,Technology (inc. Software),Asia,< 1 year,21-50,,There are many types of stakeholders,,,We are evolving an existing legacy system,,,The team is co-located in a single room,5-6 weeks,,High-level modeling using whiteboards and paper,,,Detailed modeling using whiteboards and paper,,,,,,,High-level modeling using whiteboards and paper,,,Detailed modeling using whiteboards and paper,,,,,,Detailed estimate based on traditional estimation technique,,Fixed price,Detailed schedule,,"Yes, the end date is firm due to business need",,,,We had to show that our proposed solution was technically feasible,,,,,,Yes
IT Manager,5 to 10 years,1 to 10,Technology (inc. Software),Europe,3-4 years,5-Jan,,There are many types of stakeholders,,,We are evolving an existing legacy system,,Our system integrates with legacy systems/components,The team is co-located in a single room,4 weeks,,High-level modeling using whiteboards and paper,,,,,,,,,No modeling at all,,,,,,,,,,High-level estimate based on a reasonable guess of experience person(s),,Fixed price,High-level release plan,,"Yes, we have promised an end date but it may change",,,,,,,,,Project is started when a customer signs a contract for work,No
Team Lead/Scrum Master,20+ years,1 to 10,Technology (inc. Software),North America,1-2 years,10-Jun,The team has daily access to stakeholders,There are many types of stakeholders,Regulatory compliance is an issue,This is a mission-critical project,,,,,5-6 weeks,,,,,Detailed modeling using whiteboards and paper,,,,,Industry models used as reference,,,,,Detailed modeling using whiteboards and paper,,,,Enterprise models used as reference,Industry models used as reference,High-level estimate based on agile estimation technique (e.g. planning poker),,Fixed price,Detailed schedule,,"Yes, we have promised an end date but it may change",,We had to estimate the return on investment (ROI),,We had to show that our proposed solution was technically feasible,,,,We had to show that our stakeholders agreed to the scope,,Yes
Project Manager,10 to 20 years,51 to 100,IT Consulting,Asia,< 1 year,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
QA/Test,10 to 20 years,1000+,Technology (inc. Software),North America,< 1 year,20-Nov,,,,This is a mission-critical project,,,,,> 8 weeks,No modeling at all,,,,,,,,,,No modeling at all,,,,,,,,,,Detailed estimate based on traditional estimation technique,,Time and materials,Detailed schedule,,"Yes, the end date is firm due to legislation",,We had to estimate the return on investment (ROI),,,,,,,,No
Architect,5 to 10 years,11 to 50,Technology (inc. Software),North America,1-2 years,10-Jun,The team has daily access to stakeholders,There are many types of stakeholders,,,We are evolving an existing legacy system,,,,4 weeks,,High-level modeling using whiteboards and paper,,,,,,,,,,High-level modeling using whiteboards and paper,,,,,,,,,"High-level estimate based on traditional estimation technique (e.g. COCOMO II, Function Points)",,Don't know,No initial project schedule,,"Yes, the end date is firm due to business need",,,,,,,,,,Yes
Team Lead/Scrum Master,5 to 10 years,501 to 1000,Financial,Asia,1-2 years,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Other,5 to 10 years,51 to 100,Other,Europe,5-10 years,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Other,10 to 20 years,101 to 500,Technology (inc. Software),South/Central America,< 1 year,10-Jun,The team has daily access to stakeholders,There are many types of stakeholders,,,We are evolving an existing legacy system,Our system accesses legacy data,Our system integrates with legacy systems/components,The team is co-located in a single room,3 weeks,,High-level modeling using whiteboards and paper,,,,,,Initial models were provided to us,,,,,,,,,,Initial models were provided to us,,,Detailed estimate based on agile estimation technique,,Time and materials,High-level release plan,,Don't know,,,,We had to show that our proposed solution was technically feasible,,,,We had to show that our stakeholders agreed to the scope,,No
IT Manager,10 to 20 years,51 to 100,Other,North America,< 1 year,10-Jun,The team has daily access to stakeholders,There are many types of stakeholders,Regulatory compliance is an issue,This is a mission-critical project,We are evolving an existing legacy system,Our system accesses legacy data,Our system integrates with legacy systems/components,,2 weeks,,High-level modeling using whiteboards and paper,,,,,,,,,No modeling at all,,,,,,,,,,High-level estimate based on a reasonable guess of experience person(s),,Time and materials,No initial project schedule,,"Yes, the end date is firm due to business need",,,,We had to show that our proposed solution was technically feasible,,,,,,No
Project Manager,20+ years,11 to 50,Technology (inc. Software),Australia/NZ,1-2 years,10-Jun,The team has daily access to stakeholders,,Regulatory compliance is an issue,,,Our system accesses legacy data,Our system integrates with legacy systems/components,The team is co-located in a single room,1 week,,High-level modeling using whiteboards and paper,,,Detailed modeling using whiteboards and paper,,,,Enterprise models used as reference,,,High-level modeling using whiteboards and paper,,,,,,Initial models were provided to us,,,Detailed estimate based on traditional estimation technique,,Time and materials,High-level release plan,,"Yes, the end date is firm due to legislation",,,,,,,,,Justification Provided by business need,No
Project Manager,20+ years,101 to 500,Technology (inc. Software),North America,None,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Team Lead/Scrum Master,10 to 20 years,11 to 50,Other,North America,< 1 year,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Project Manager,20+ years,101 to 500,Technology (inc. Software),North America,None,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Programmer,10 to 20 years,51 to 100,Other,Europe,< 1 year,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Team Lead/Scrum Master,10 to 20 years,1000+,Technology (inc. Software),North America,3-4 years,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Architect,5 to 10 years,1 to 10,Government,South/Central America,< 1 year,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Team Lead/Scrum Master,20+ years,1000+,Technology (inc. Software),North America,5-10 years,10-Jun,The team has daily access to stakeholders,There are many types of stakeholders,,This is a mission-critical project,,Our system accesses legacy data,Our system integrates with legacy systems/components,The team is co-located in a single room,2 weeks,,High-level modeling using whiteboards and paper,,,,,,,,,,,,,Detailed modeling using whiteboards and paper,,,,,,Detailed estimate based on agile estimation technique,,Staged-gate funding,High-level release plan,,"Yes, we have promised an end date but it may change",,,,We had to show that our proposed solution was technically feasible,We had to show that our proposed solution could be supported by our operations group,We had to show that we considered commercial packages,We had to show that we considered offshoring the project,,,Yes
Product Owner,20+ years,1 to 10,Technology (inc. Software),North America,1-2 years,20-Nov,The team has daily access to stakeholders,There are many types of stakeholders,Regulatory compliance is an issue,,We are evolving an existing legacy system,Our system accesses legacy data,Our system integrates with legacy systems/components,,2 weeks,,High-level modeling using whiteboards and paper,High-level modeling using drawing tools,,Detailed modeling using whiteboards and paper,Detailed modeling using drawing tools,,,,,,High-level modeling using whiteboards and paper,High-level modeling using drawing tools,,Detailed modeling using whiteboards and paper,Detailed modeling using drawing tools,,,,,High-level estimate based on agile estimation technique (e.g. planning poker),,Staged-gate funding,High-level release plan,,"Yes, the end date is firm due to business need",,,,We had to show that our proposed solution was technically feasible,,,,We had to show that our stakeholders agreed to the scope,,No
Team Lead/Scrum Master,20+ years,101 to 500,Financial,North America,5-10 years,20-Nov,The team has daily access to stakeholders,There are many types of stakeholders,Regulatory compliance is an issue,,We are evolving an existing legacy system,Our system accesses legacy data,Our system integrates with legacy systems/components,,3 weeks,,,High-level modeling using drawing tools,,,,,,,,,High-level modeling using whiteboards and paper,,,,,,,,,High-level estimate based on agile estimation technique (e.g. planning poker),,Fixed price,High-level release plan,,"Yes, we have promised an end date but it may change",,We had to estimate the return on investment (ROI),,,We had to show that our proposed solution could be supported by our operations group,We had to show that we considered commercial packages,,,,Yes
Project Manager,10 to 20 years,51 to 100,Technology (inc. Software),North America,None,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Other,10 to 20 years,51 to 100,Technology (inc. Software),North America,5-10 years,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Project Manager,20+ years,1 to 10,IT Consulting,Europe,3-4 years,5-Jan,,There are many types of stakeholders,Regulatory compliance is an issue,,We are evolving an existing legacy system,,,,1 week,,High-level modeling using whiteboards and paper,,,Detailed modeling using whiteboards and paper,,,,,,,High-level modeling using whiteboards and paper,,,Detailed modeling using whiteboards and paper,,Detailed modeling using modeling/CASE tools,,,,High-level estimate based on a reasonable guess of experience person(s),,Fixed price,High-level release plan,,"Yes, the end date is firm due to legislation",,,,We had to show that our proposed solution was technically feasible,,We had to show that we considered commercial packages,,We had to show that our stakeholders agreed to the scope,,Yes
IT Manager,20+ years,1000+,Financial,Europe,1-2 years,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Project Manager,2 to 5 years,11 to 50,Financial,North America,3-4 years,5-Jan,The team has daily access to stakeholders,,,This is a mission-critical project,,,Our system integrates with legacy systems/components,The team is co-located in a single room,7-8 weeks,,High-level modeling using whiteboards and paper,,,,,,,,Industry models used as reference,,,,,Detailed modeling using whiteboards and paper,,,,,Industry models used as reference,No initial estimate at all,,Staged-gate funding,High-level release plan,,"Yes, the end date is firm due to business need","The end date is firm, but the feature set is not.",We had to estimate the return on investment (ROI),,We had to show that our proposed solution was technically feasible,,,,,,Yes
Other,None,1 to 10,Financial,South/Central America,< 1 year,5-Jan,The team has daily access to stakeholders,There are many types of stakeholders,,,,,,The team is co-located in a single room,2 weeks,,,,,,,,,,,,,,,,,,,,,High-level estimate based on agile estimation technique (e.g. planning poker),,Don't know,Don't know,,Don't know,,We had to estimate the return on investment (ROI),,,,,,,,No
Team Lead/Scrum Master,2 to 5 years,1 to 10,Technology (inc. Software),North America,< 1 year,5-Jan,The team has daily access to stakeholders,,,,,,,The team is co-located in a single room,2 weeks,,High-level modeling using whiteboards and paper,,,,,,,Enterprise models used as reference,,,High-level modeling using whiteboards and paper,,,,,,,Enterprise models used as reference,,"High-level estimate based on traditional estimation technique (e.g. COCOMO II, Function Points)",,Don't know,High-level release plan,,"Yes, we have promised an end date but it may change",,We had to estimate the return on investment (ROI),,We had to show that our proposed solution was technically feasible,,,,,,Yes
IT Manager,20+ years,51 to 100,Government,North America,1-2 years,10-Jun,The team has daily access to stakeholders,There are many types of stakeholders,,This is a mission-critical project,We are evolving an existing legacy system,,,The team is co-located in a single room,3 weeks,,High-level modeling using whiteboards and paper,,,,,,Initial models were provided to us,Enterprise models used as reference,,,High-level modeling using whiteboards and paper,,,,,,Initial models were provided to us,Enterprise models used as reference,Industry models used as reference,Detailed estimate based on a reasonable guess of experience person(s),,Fixed price,Detailed schedule,,"Yes, the end date is firm due to business need",,We had to estimate the return on investment (ROI),,We had to show that our proposed solution was technically feasible,We had to show that our proposed solution could be supported by our operations group,,,We had to show that our stakeholders agreed to the scope,,Yes
Team Lead/Scrum Master,10 to 20 years,11 to 50,IT Consulting,North America,5-10 years,5-Jan,,There are many types of stakeholders,,This is a mission-critical project,We are evolving an existing legacy system,Our system accesses legacy data,Our system integrates with legacy systems/components,The team is co-located in a single room,3 weeks,No modeling at all,High-level modeling using whiteboards and paper,High-level modeling using drawing tools,,,,,,,,No modeling at all,High-level modeling using whiteboards and paper,,,,,,,,,High-level estimate based on agile estimation technique (e.g. planning poker),,Don't know,High-level release plan,,"Yes, we have promised an end date but it may change",,We had to estimate the return on investment (ROI),,,,,,We had to show that our stakeholders agreed to the scope,,No
IT Manager,10 to 20 years,1000+,Other,Europe,3-4 years,20-Nov,The team has daily access to stakeholders,There are many types of stakeholders,,This is a mission-critical project,We are evolving an existing legacy system,Our system accesses legacy data,Our system integrates with legacy systems/components,,5-6 weeks,,,High-level modeling using drawing tools,,,,,,,Industry models used as reference,,,High-level modeling using drawing tools,,,,,,,,High-level estimate based on a reasonable guess of experience person(s),,Fixed price,High-level release plan,,"No, we are still negotiating",,We had to estimate the return on investment (ROI),,We had to show that our proposed solution was technically feasible,We had to show that our proposed solution could be supported by our operations group,We had to show that we considered commercial packages,We had to show that we considered offshoring the project,We had to show that our stakeholders agreed to the scope,,Yes
Product Owner,5 to 10 years,501 to 1000,Technology (inc. Software),Europe,1-2 years,10-Jun,,There are many types of stakeholders,,This is a mission-critical project,,,,,7-8 weeks,,,,,,Detailed modeling using drawing tools,,,,,,High-level modeling using whiteboards and paper,,,,,,,,,High-level estimate based on agile estimation technique (e.g. planning poker),,Time and materials,High-level release plan,,"Yes, we have promised an end date but it may change",,,,,,,,We had to show that our stakeholders agreed to the scope,,Yes
Business Analyst,10 to 20 years,11 to 50,Retail,North America,3-4 years,20-Nov,The team has daily access to stakeholders,There are many types of stakeholders,,This is a mission-critical project,We are evolving an existing legacy system,,,,< 1 week,No modeling at all,,,,,,,,,,No modeling at all,,,,,,,,,,Detailed estimate based on traditional estimation technique,,Time and materials,High-level release plan,,"Yes, we have promised an end date but it may change",,,,,,,,We had to show that our stakeholders agreed to the scope,,No
Agile Team Member,10 to 20 years,1 to 10,Technology (inc. Software),North America,< 1 year,5-Jan,,There are many types of stakeholders,,,,,,,3 weeks,,,,High-level modeling using modeling/CASE tools,,,,,,,,High-level modeling using whiteboards and paper,,,,,,,,,No initial estimate at all,,Don't know,No initial project schedule,,"No, we are still negotiating",,,,,,,,,,No
Team Lead/Scrum Master,5 to 10 years,1 to 10,Government,Europe,5-10 years,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Team Lead/Scrum Master,5 to 10 years,11 to 50,IT Consulting,Europe,< 1 year,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Team Lead/Scrum Master,10 to 20 years,11 to 50,IT Consulting,Europe,1-2 years,5-Jan,The team has daily access to stakeholders,,,This is a mission-critical project,We are evolving an existing legacy system,,,,2 weeks,,High-level modeling using whiteboards and paper,,,,,,,,,,High-level modeling using whiteboards and paper,,,,,,,,,Detailed estimate based on agile estimation technique,,Fixed price,High-level release plan,,"Yes, the end date is firm due to business need",,,,,,,,We had to show that our stakeholders agreed to the scope,,Yes
Other,20+ years,1000+,Retail,North America,< 1 year,10-Jun,The team has daily access to stakeholders,There are many types of stakeholders,Regulatory compliance is an issue,,We are evolving an existing legacy system,Our system accesses legacy data,Our system integrates with legacy systems/components,,> 8 weeks,,High-level modeling using whiteboards and paper,,,,,,,,,,,High-level modeling using drawing tools,,,,,,,,High-level estimate based on a reasonable guess of experience person(s),,Staged-gate funding,Don't know,,"Yes, we have promised an end date but it may change",,We had to estimate the return on investment (ROI),,,,,,We had to show that our stakeholders agreed to the scope,,Yes
Agile Team Member,5 to 10 years,11 to 50,Manufacturing,North America,5-10 years,10-Jun,,There are many types of stakeholders,Regulatory compliance is an issue,This is a mission-critical project,We are evolving an existing legacy system,Our system accesses legacy data,Our system integrates with legacy systems/components,,2 weeks,,High-level modeling using whiteboards and paper,High-level modeling using drawing tools,,,,,,,Industry models used as reference,,High-level modeling using whiteboards and paper,,,,,,,,,High-level estimate based on agile estimation technique (e.g. planning poker),,Don't know,High-level release plan,,"Yes, the end date is firm due to business need",,We had to estimate the return on investment (ROI),We had to estimate the net present value (NPV),,,We had to show that we considered commercial packages,,,,No
Project Manager,5 to 10 years,11 to 50,Technology (inc. Software),Europe,1-2 years,5-Jan,,There are many types of stakeholders,,This is a mission-critical project,,,,,2 weeks,,High-level modeling using whiteboards and paper,,,Detailed modeling using whiteboards and paper,,,,,,,High-level modeling using whiteboards and paper,,,Detailed modeling using whiteboards and paper,,,,,,Detailed estimate based on a reasonable guess of experience person(s),,Fixed price,High-level release plan,,"Yes, the end date is firm due to business need",,,,We had to show that our proposed solution was technically feasible,We had to show that our proposed solution could be supported by our operations group,,,We had to show that our stakeholders agreed to the scope,,Yes
Project Manager,10 to 20 years,1 to 10,e-Commerce,Europe,1-2 years,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Team Lead/Scrum Master,10 to 20 years,11 to 50,Other,North America,3-4 years,10-Jun,,,,,We are evolving an existing legacy system,Our system accesses legacy data,Our system integrates with legacy systems/components,,> 8 weeks,No modeling at all,,,,,,,,,,,,High-level modeling using drawing tools,,,,,,Enterprise models used as reference,Industry models used as reference,High-level estimate based on agile estimation technique (e.g. planning poker),,Don't know,High-level release plan,,"Yes, we have promised an end date but it may change",,,,We had to show that our proposed solution was technically feasible,We had to show that our proposed solution could be supported by our operations group,We had to show that we considered commercial packages,We had to show that we considered offshoring the project,We had to show that our stakeholders agreed to the scope,,No
Project Manager,10 to 20 years,101 to 500,Financial,Europe,5-10 years,20-Nov,,There are many types of stakeholders,,,,,Our system integrates with legacy systems/components,The team is co-located in a single room,1 week,,,High-level modeling using drawing tools,,,,,Initial models were provided to us,,,,,High-level modeling using drawing tools,,,,,,,Industry models used as reference,High-level estimate based on a reasonable guess of experience person(s),,Staged-gate funding,High-level release plan,,"Yes, the end date is firm due to business need",,,,We had to show that our proposed solution was technically feasible,We had to show that our proposed solution could be supported by our operations group,,,,,Yes
Programmer,5 to 10 years,101 to 500,Other,Europe,< 1 year,10-Jun,The team has daily access to stakeholders,,,,,,,The team is co-located in a single room,4 weeks,,,,,,,,,,,,,,,,,,,,,High-level estimate based on agile estimation technique (e.g. planning poker),,Time and materials,Detailed schedule,,"Yes, the end date is firm due to business need",,,,,,,,,,Yes
Agile Team Member,2 to 5 years,1 to 10,Technology (inc. Software),Europe,1-2 years,5-Jan,The team has daily access to stakeholders,,,This is a mission-critical project,We are evolving an existing legacy system,,Our system integrates with legacy systems/components,The team is co-located in a single room,3 weeks,,High-level modeling using whiteboards and paper,,,,,,,,,,High-level modeling using whiteboards and paper,,,,,,,,,High-level estimate based on agile estimation technique (e.g. planning poker),,Fixed price,High-level release plan,,"Yes, the end date is firm due to business need",,,,,,,,,,Yes
Project Manager,5 to 10 years,11 to 50,e-Commerce,Europe,3-4 years,10-Jun,The team has daily access to stakeholders,There are many types of stakeholders,,This is a mission-critical project,We are evolving an existing legacy system,,,,5-6 weeks,,High-level modeling using whiteboards and paper,High-level modeling using drawing tools,,,,,,,,,,,,,,,Initial models were provided to us,Enterprise models used as reference,,High-level estimate based on a reasonable guess of experience person(s),,Staged-gate funding,High-level release plan,,"No, we will ship when our stakeholders tell us to",,,,,,,,We had to show that our stakeholders agreed to the scope,,Yes
Project Manager,10 to 20 years,51 to 100,Technology (inc. Software),Europe,1-2 years,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Architect,10 to 20 years,11 to 50,IT Consulting,Europe,5-10 years,10-Jun,,There are many types of stakeholders,,,We are evolving an existing legacy system,Our system accesses legacy data,,,5-6 weeks,,,,,,,,Initial models were provided to us,,,,High-level modeling using whiteboards and paper,,,,,,,,,"High-level estimate based on traditional estimation technique (e.g. COCOMO II, Function Points)",,Fixed price,High-level release plan,,"Yes, the end date is firm due to business need",,,,We had to show that our proposed solution was technically feasible,,,,,,No
Architect,5 to 10 years,101 to 500,Financial,Europe,3-4 years,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Team Lead/Scrum Master,20+ years,1 to 10,Technology (inc. Software),North America,5-10 years,10-Jun,,,Regulatory compliance is an issue,,We are evolving an existing legacy system,,,The team is co-located in a single room,1 week,,High-level modeling using whiteboards and paper,,,,,,,,,,High-level modeling using whiteboards and paper,High-level modeling using drawing tools,,,,,,,,High-level estimate based on a reasonable guess of experience person(s),,Fixed price,High-level release plan,,"Yes, we have promised an end date but it may change",,,,We had to show that our proposed solution was technically feasible,,,,We had to show that our stakeholders agreed to the scope,,No
Team Lead/Scrum Master,10 to 20 years,11 to 50,Other,Europe,3-4 years,10-Jun,The team has daily access to stakeholders,There are many types of stakeholders,,,,,Our system integrates with legacy systems/components,The team is co-located in a single room,2 weeks,,High-level modeling using whiteboards and paper,,,,,,,,,,High-level modeling using whiteboards and paper,,,,,,,,,High-level estimate based on agile estimation technique (e.g. planning poker),,Staged-gate funding,High-level release plan,,"Yes, the end date is firm due to business need",,,,We had to show that our proposed solution was technically feasible,We had to show that our proposed solution could be supported by our operations group,,,We had to show that our stakeholders agreed to the scope,,Yes
Programmer,2 to 5 years,1 to 10,Manufacturing,North America,< 1 year,5-Jan,The team has daily access to stakeholders,,,This is a mission-critical project,We are evolving an existing legacy system,Our system accesses legacy data,Our system integrates with legacy systems/components,,5-6 weeks,,,High-level modeling using drawing tools,,,,,Initial models were provided to us,,,,,,,,Detailed modeling using drawing tools,,,,,High-level estimate based on a reasonable guess of experience person(s),,Time and materials,Detailed schedule,,"Yes, we have promised an end date but it may change",,We had to estimate the return on investment (ROI),,We had to show that our proposed solution was technically feasible,,,,,,Yes
Project Manager,10 to 20 years,1 to 10,Financial,Europe,1-2 years,10-Jun,,,,,,Our system accesses legacy data,,The team is co-located in a single room,2 weeks,,High-level modeling using whiteboards and paper,,,,,,,,,,High-level modeling using whiteboards and paper,,,Detailed modeling using whiteboards and paper,,,,,,High-level estimate based on a reasonable guess of experience person(s),,Time and materials,High-level release plan,,"Yes, we have promised an end date but it may change",,,,We had to show that our proposed solution was technically feasible,,,,We had to show that our stakeholders agreed to the scope,,Yes
Architect,5 to 10 years,51 to 100,Technology (inc. Software),North America,3-4 years,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Other,5 to 10 years,51 to 100,IT Consulting,Europe,5-10 years,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Project Manager,2 to 5 years,11 to 50,Other,Europe,< 1 year,21-50,,,,,,,,The team is co-located in a single room,< 1 week,,,,,Detailed modeling using whiteboards and paper,,,,,Industry models used as reference,,High-level modeling using whiteboards and paper,,,Detailed modeling using whiteboards and paper,,,,,,"High-level estimate based on traditional estimation technique (e.g. COCOMO II, Function Points)",,Time and materials,High-level release plan,,"Yes, we have promised an end date but it may change",,We had to estimate the return on investment (ROI),,,,,,,,Yes
Agile Team Member,2 to 5 years,1 to 10,Technology (inc. Software),Europe,1-2 years,10-Jun,The team has daily access to stakeholders,There are many types of stakeholders,,This is a mission-critical project,,,,,Don't know,,High-level modeling using whiteboards and paper,,,,,,,,,,High-level modeling using whiteboards and paper,,,,,,,,Industry models used as reference,High-level estimate based on a reasonable guess of experience person(s),,Fixed price,High-level release plan,,"Yes, the end date is firm due to business need",,,,,,,,,,Don't Know
Other,10 to 20 years,1 to 10,Technology (inc. Software),Asia,< 1 year,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Team Lead/Scrum Master,5 to 10 years,11 to 50,IT Consulting,Europe,3-4 years,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Team Lead/Scrum Master,Less than 2 years,11 to 50,Technology (inc. Software),Europe,1-2 years,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Business Analyst,5 to 10 years,51 to 100,Retail,Europe,< 1 year,10-Jun,,There are many types of stakeholders,,,We are evolving an existing legacy system,,Our system integrates with legacy systems/components,The team is co-located in a single room,2 weeks,No modeling at all,,,,,,,,,,,,,,,,,Initial models were provided to us,,,High-level estimate based on agile estimation technique (e.g. planning poker),,Don't know,High-level release plan,,"No, we are still negotiating",,,,,,,,We had to show that our stakeholders agreed to the scope,,Yes
Other,10 to 20 years,1000+,IT Consulting,Europe,3-4 years,5-Jan,The team has daily access to stakeholders,,,,,,Our system integrates with legacy systems/components,The team is co-located in a single room,3 weeks,No modeling at all,,,,,,,,,,No modeling at all,,,,,,,,,,High-level estimate based on a reasonable guess of experience person(s),,Fixed price,No initial project schedule,,"Yes, the end date is firm due to business need",,,,We had to show that our proposed solution was technically feasible,,,,,,Yes
Programmer,20+ years,1 to 10,Other,North America,1-2 years,5-Jan,The team has daily access to stakeholders,,,,,,,,Don't know,,High-level modeling using whiteboards and paper,,,,,,,,,,High-level modeling using whiteboards and paper,,,,,,,,,Don't know,,Staged-gate funding,High-level release plan,,"No, we are still negotiating",,,,,,,,,,Yes
IT Manager,5 to 10 years,51 to 100,Technology (inc. Software),Europe,5-10 years,10-Jun,The team has daily access to stakeholders,There are many types of stakeholders,Regulatory compliance is an issue,This is a mission-critical project,We are evolving an existing legacy system,Our system accesses legacy data,Our system integrates with legacy systems/components,The team is co-located in a single room,2 weeks,,,,,,,,Initial models were provided to us,,,,High-level modeling using whiteboards and paper,High-level modeling using drawing tools,,,,,,,,Detailed estimate based on agile estimation technique,,Time and materials,High-level release plan,,"Yes, the end date is firm due to business need",,,,,,,,,,No
Team Lead/Scrum Master,10 to 20 years,101 to 500,Financial,Europe,3-4 years,10-Jun,The team has daily access to stakeholders,,,,We are evolving an existing legacy system,Our system accesses legacy data,Our system integrates with legacy systems/components,The team is co-located in a single room,2 weeks,,High-level modeling using whiteboards and paper,,High-level modeling using modeling/CASE tools,,,,,,,,High-level modeling using whiteboards and paper,,,,,,,Enterprise models used as reference,,High-level estimate based on agile estimation technique (e.g. planning poker),,Time and materials,High-level release plan,,"Yes, the end date is firm due to legislation",,,,,,,,,,Yes
IT Manager,10 to 20 years,1 to 10,Technology (inc. Software),North America,3-4 years,5-Jan,The team has daily access to stakeholders,There are many types of stakeholders,,,,Our system accesses legacy data,Our system integrates with legacy systems/components,The team is co-located in a single room,2 weeks,,High-level modeling using whiteboards and paper,,,,,,,,,,High-level modeling using whiteboards and paper,,,,,,,,,Detailed estimate based on agile estimation technique,,Fixed price,High-level release plan,,"Yes, we have promised an end date but it may change",,,,,We had to show that our proposed solution could be supported by our operations group,,,,,No
Team Lead/Scrum Master,5 to 10 years,101 to 500,Technology (inc. Software),Asia,3-4 years,10-Jun,,There are many types of stakeholders,,,We are evolving an existing legacy system,,,The team is co-located in a single room,4 weeks,No modeling at all,High-level modeling using whiteboards and paper,,High-level modeling using modeling/CASE tools,,,,,,,,,,High-level modeling using modeling/CASE tools,,,,,,,"High-level estimate based on traditional estimation technique (e.g. COCOMO II, Function Points)",,Fixed price,High-level release plan,,"Yes, the end date is firm due to business need",,We had to estimate the return on investment (ROI),,,,,,We had to show that our stakeholders agreed to the scope,,Yes
Programmer,5 to 10 years,11 to 50,IT Consulting,Europe,5-10 years,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Project Manager,5 to 10 years,101 to 500,Government,North America,1-2 years,20-Nov,The team has daily access to stakeholders,There are many types of stakeholders,Regulatory compliance is an issue,This is a mission-critical project,,,,The team is co-located in a single room,7-8 weeks,,High-level modeling using whiteboards and paper,,,,,,,,,,High-level modeling using whiteboards and paper,,,,,,,,,High-level estimate based on a reasonable guess of experience person(s),,Don't know,Don't know,High level schedule,"Yes, we have promised an end date but it may change",,,,,,,,We had to show that our stakeholders agreed to the scope,,Yes
Team Lead/Scrum Master,10 to 20 years,101 to 500,Technology (inc. Software),Europe,1-2 years,5-Jan,,There are many types of stakeholders,Regulatory compliance is an issue,This is a mission-critical project,We are evolving an existing legacy system,Our system accesses legacy data,Our system integrates with legacy systems/components,The team is co-located in a single room,> 8 weeks,,High-level modeling using whiteboards and paper,,,,Detailed modeling using drawing tools,,,,Industry models used as reference,,High-level modeling using whiteboards and paper,,,,Detailed modeling using drawing tools,,Initial models were provided to us,,,Detailed estimate based on a reasonable guess of experience person(s),,Staged-gate funding,High-level release plan,,"Yes, we have promised an end date but it may change",,,,,,,,We had to show that our stakeholders agreed to the scope,,Yes
Project Manager,10 to 20 years,51 to 100,Technology (inc. Software),Africa,5-10 years,20-Nov,The team has daily access to stakeholders,There are many types of stakeholders,Regulatory compliance is an issue,,We are evolving an existing legacy system,,Our system integrates with legacy systems/components,The team is co-located in a single room,> 8 weeks,,High-level modeling using whiteboards and paper,,High-level modeling using modeling/CASE tools,Detailed modeling using whiteboards and paper,,Detailed modeling using modeling/CASE tools,,,Industry models used as reference,,High-level modeling using whiteboards and paper,,High-level modeling using modeling/CASE tools,Detailed modeling using whiteboards and paper,,Detailed modeling using modeling/CASE tools,,Enterprise models used as reference,Industry models used as reference,High-level estimate based on a reasonable guess of experience person(s),,Time and materials,High-level release plan,,"Yes, we have promised an end date but it may change",,,,We had to show that our proposed solution was technically feasible,,We had to show that we considered commercial packages,,We had to show that our stakeholders agreed to the scope,,Yes
Architect,10 to 20 years,11 to 50,Technology (inc. Software),Asia,1-2 years,10-Jun,The team has daily access to stakeholders,There are many types of stakeholders,,This is a mission-critical project,,,,The team is co-located in a single room,2 weeks,,,,High-level modeling using modeling/CASE tools,,,,,,,,High-level modeling using whiteboards and paper,,,,,Detailed modeling using modeling/CASE tools,,,,High-level estimate based on a reasonable guess of experience person(s),,Fixed price,High-level release plan,,"Yes, the end date is firm due to business need",,,,We had to show that our proposed solution was technically feasible,,,,We had to show that our stakeholders agreed to the scope,,Yes
Product Owner,10 to 20 years,1 to 10,Financial,Africa,3-4 years,5-Jan,The team has daily access to stakeholders,There are many types of stakeholders,Regulatory compliance is an issue,This is a mission-critical project,We are evolving an existing legacy system,,,,Don't know,,High-level modeling using whiteboards and paper,,,,,,,,,,High-level modeling using whiteboards and paper,,,,,,,,Industry models used as reference,High-level estimate based on a reasonable guess of experience person(s),,Time and materials,Don't know,,"Yes, we have promised an end date but it may change",,,,,,,,,,Don't Know
Architect,10 to 20 years,1000+,Retail,North America,3-4 years,501+,The team has daily access to stakeholders,There are many types of stakeholders,Regulatory compliance is an issue,This is a mission-critical project,We are evolving an existing legacy system,Our system accesses legacy data,Our system integrates with legacy systems/components,,> 8 weeks,,High-level modeling using whiteboards and paper,High-level modeling using drawing tools,,Detailed modeling using whiteboards and paper,Detailed modeling using drawing tools,,,Enterprise models used as reference,Industry models used as reference,,High-level modeling using whiteboards and paper,High-level modeling using drawing tools,,,Detailed modeling using drawing tools,Detailed modeling using modeling/CASE tools,,Enterprise models used as reference,Industry models used as reference,"High-level estimate based on traditional estimation technique (e.g. COCOMO II, Function Points)",,Staged-gate funding,High-level release plan,,"Yes, the end date is firm due to business need",,We had to estimate the return on investment (ROI),,We had to show that our proposed solution was technically feasible,We had to show that our proposed solution could be supported by our operations group,We had to show that we considered commercial packages,We had to show that we considered offshoring the project,We had to show that our stakeholders agreed to the scope,,Yes
Project Manager,5 to 10 years,101 to 500,IT Consulting,Europe,3-4 years,20-Nov,,There are many types of stakeholders,,,We are evolving an existing legacy system,Our system accesses legacy data,Our system integrates with legacy systems/components,The team is co-located in a single room,> 8 weeks,,,,,Detailed modeling using whiteboards and paper,,,,,,,High-level modeling using whiteboards and paper,High-level modeling using drawing tools,,,,,,Enterprise models used as reference,Industry models used as reference,High-level estimate based on a reasonable guess of experience person(s),,Fixed price,High-level release plan,,"Yes, we have promised an end date but it may change",,We had to estimate the return on investment (ROI),,We had to show that our proposed solution was technically feasible,,,,We had to show that our stakeholders agreed to the scope,,Yes
Other,20+ years,101 to 500,Other,North America,5-10 years,21-50,,There are many types of stakeholders,,,,Our system accesses legacy data,Our system integrates with legacy systems/components,,> 8 weeks,,High-level modeling using whiteboards and paper,,,,,,,,,No modeling at all,,,,,,,,,,High-level estimate based on a reasonable guess of experience person(s),,Don't know,High-level release plan,,"Yes, we have promised an end date but it may change",,,,,,,,We had to show that our stakeholders agreed to the scope,,Yes
Project Manager,10 to 20 years,1000+,Technology (inc. Software),North America,1-2 years,20-Nov,The team has daily access to stakeholders,There are many types of stakeholders,,,,,,,< 1 week,No modeling at all,,,,,,,,,,No modeling at all,,,,,,,,,,High-level estimate based on agile estimation technique (e.g. planning poker),,Don't know,No initial project schedule,,"No, we will ship when our stakeholders tell us to",,,,,,,,,,Yes
Architect,20+ years,1000+,IT Consulting,North America,5-10 years,20-Nov,,There are many types of stakeholders,Regulatory compliance is an issue,,We are evolving an existing legacy system,Our system accesses legacy data,Our system integrates with legacy systems/components,,4 weeks,,High-level modeling using whiteboards and paper,,,,,,,Enterprise models used as reference,,,,High-level modeling using drawing tools,High-level modeling using modeling/CASE tools,,,,,Enterprise models used as reference,,High-level estimate based on a reasonable guess of experience person(s),,Time and materials,High-level release plan,,"Yes, the end date is firm due to business need",,,,We had to show that our proposed solution was technically feasible,We had to show that our proposed solution could be supported by our operations group,,,We had to show that our stakeholders agreed to the scope,,Yes
Agile Team Member,2 to 5 years,11 to 50,IT Consulting,North America,1-2 years,5-Jan,The team has daily access to stakeholders,There are many types of stakeholders,,,We are evolving an existing legacy system,Our system accesses legacy data,Our system integrates with legacy systems/components,,1 week,,High-level modeling using whiteboards and paper,,,,,,,,,No modeling at all,,,,,,,,,,No initial estimate at all,,Time and materials,No initial project schedule,,"No, we will ship when our stakeholders tell us to",,,,,,,,We had to show that our stakeholders agreed to the scope,,Don't Know
Team Lead/Scrum Master,10 to 20 years,1 to 10,Technology (inc. Software),North America,3-4 years,5-Jan,The team has daily access to stakeholders,,,,We are evolving an existing legacy system,,,,1 week,,High-level modeling using whiteboards and paper,,,,,,,Enterprise models used as reference,,,,,,,,,,Enterprise models used as reference,,No initial estimate at all,,Don't know,High-level release plan,,Don't know,Ship every month until we run out of ideas or customers,,,,,,,,,No
Team Lead/Scrum Master,5 to 10 years,1 to 10,IT Consulting,North America,3-4 years,5-Jan,The team has daily access to stakeholders,There are many types of stakeholders,,,,Our system accesses legacy data,Our system integrates with legacy systems/components,,2 weeks,,High-level modeling using whiteboards and paper,,,,,,,,,,High-level modeling using whiteboards and paper,,,,,,,,,High-level estimate based on agile estimation technique (e.g. planning poker),,Time and materials,High-level release plan,,"No, we will ship when our stakeholders tell us to",,,,,,,,We had to show that our stakeholders agreed to the scope,,No
Business Analyst,20+ years,101 to 500,IT Consulting,North America,None,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Programmer,5 to 10 years,1 to 10,Financial,South/Central America,None,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Project Manager,10 to 20 years,101 to 500,Technology (inc. Software),North America,5-10 years,20-Nov,The team has daily access to stakeholders,,,,We are evolving an existing legacy system,,,,Don't know,,High-level modeling using whiteboards and paper,,,Detailed modeling using whiteboards and paper,,,,Enterprise models used as reference,Industry models used as reference,,High-level modeling using whiteboards and paper,,,Detailed modeling using whiteboards and paper,,,,Enterprise models used as reference,Industry models used as reference,High-level estimate based on a reasonable guess of experience person(s),,Fixed price,High-level release plan,,"Yes, the end date is firm due to business need",,,,,,,,We had to show that our stakeholders agreed to the scope,,Yes
IT Manager,10 to 20 years,101 to 500,Other,North America,3-4 years,10-Jun,,There are many types of stakeholders,Regulatory compliance is an issue,This is a mission-critical project,We are evolving an existing legacy system,Our system accesses legacy data,Our system integrates with legacy systems/components,,< 1 week,,High-level modeling using whiteboards and paper,,,,,,,Enterprise models used as reference,,,High-level modeling using whiteboards and paper,,,Detailed modeling using whiteboards and paper,,,,Enterprise models used as reference,,Detailed estimate based on agile estimation technique,,Don't know,High-level release plan,,"Yes, the end date is firm due to business need",,We had to estimate the return on investment (ROI),,,,,,We had to show that our stakeholders agreed to the scope,,Yes
Business Analyst,2 to 5 years,1000+,Financial,South/Central America,None,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Other,20+ years,1000+,Government,Europe,< 1 year,10-Jun,The team has daily access to stakeholders,,Regulatory compliance is an issue,,We are evolving an existing legacy system,Our system accesses legacy data,Our system integrates with legacy systems/components,The team is co-located in a single room,3 weeks,,,,,,,Detailed modeling using modeling/CASE tools,,,,,,,,,,,,Enterprise models used as reference,,"High-level estimate based on traditional estimation technique (e.g. COCOMO II, Function Points)",,Fixed price,High-level release plan,,"Yes, the end date is firm due to legislation",,,,We had to show that our proposed solution was technically feasible,We had to show that our proposed solution could be supported by our operations group,,,We had to show that our stakeholders agreed to the scope,,Yes
Product Owner,5 to 10 years,1 to 10,Technology (inc. Software),Asia,5-10 years,5-Jan,The team has daily access to stakeholders,,,,,,,The team is co-located in a single room,3 weeks,,High-level modeling using whiteboards and paper,,,,,,,,,,High-level modeling using whiteboards and paper,,,,,,,,,No initial estimate at all,,Time and materials,No initial project schedule,,"No, we will ship when our stakeholders tell us to",,,,We had to show that our proposed solution was technically feasible,,,,,We had to validate the product concept,Yes
Business Analyst,10 to 20 years,101 to 500,Government,North America,5-10 years,20-Nov,,There are many types of stakeholders,,This is a mission-critical project,,Our system accesses legacy data,Our system integrates with legacy systems/components,,Don't know,No modeling at all,,,,,,,,,,No modeling at all,,,,,,,,,,High-level estimate based on a reasonable guess of experience person(s),,Fixed price,High-level release plan,,"Yes, the end date is firm due to business need",,,,,,,,,No,Don't Know
Architect,20+ years,1 to 10,Technology (inc. Software),North America,> 10 years,5-Jan,The team has daily access to stakeholders,There are many types of stakeholders,Regulatory compliance is an issue,This is a mission-critical project,,Our system accesses legacy data,Our system integrates with legacy systems/components,,< 1 week,,High-level modeling using whiteboards and paper,,,Detailed modeling using whiteboards and paper,,,,,,,,,,,,Detailed modeling using modeling/CASE tools,,,,Detailed estimate based on a reasonable guess of experience person(s),"Estimate based upon experience with a ""home-built"" system framework and component generation system",Fixed price,High-level release plan,,"Yes, the end date is firm due to legislation",,,,,,,,,Modest funding requirement was offset by substantial late penalties to be levied by regulatory agency.,No
Programmer,10 to 20 years,101 to 500,Technology (inc. Software),North America,1-2 years,10-Jun,The team has daily access to stakeholders,,,,We are evolving an existing legacy system,,,The team is co-located in a single room,Don't know,,,,,,Detailed modeling using drawing tools,,,,,,,,,,Detailed modeling using drawing tools,,,,,High-level estimate based on agile estimation technique (e.g. planning poker),,Don't know,High-level release plan,,"Yes, the end date is firm due to business need",,,,,,,,We had to show that our stakeholders agreed to the scope,,No
Other,20+ years,11 to 50,Technology (inc. Software),North America,3-4 years,21-50,,There are many types of stakeholders,Regulatory compliance is an issue,This is a mission-critical project,We are evolving an existing legacy system,Our system accesses legacy data,Our system integrates with legacy systems/components,,> 8 weeks,,,,,Detailed modeling using whiteboards and paper,,,,,Industry models used as reference,,,,,,,,Initial models were provided to us,,,"High-level estimate based on traditional estimation technique (e.g. COCOMO II, Function Points)",,Fixed price,High-level release plan,,"Yes, we have promised an end date but it may change",,,,We had to show that our proposed solution was technically feasible,,,,,,No
Agile Team Member,10 to 20 years,1 to 10,Technology (inc. Software),Australia/NZ,5-10 years,10-Jun,The team has daily access to stakeholders,There are many types of stakeholders,Regulatory compliance is an issue,,,,,,7-8 weeks,,,,,,,,,,Industry models used as reference,,High-level modeling using whiteboards and paper,,,,,,,,,High-level estimate based on a reasonable guess of experience person(s),,Time and materials,No initial project schedule,,"No, we will ship when our stakeholders tell us to",,,,We had to show that our proposed solution was technically feasible,,,,,,Yes
Project Manager,10 to 20 years,1 to 10,IT Consulting,North America,3-4 years,10-Jun,The team has daily access to stakeholders,There are many types of stakeholders,,This is a mission-critical project,We are evolving an existing legacy system,Our system accesses legacy data,,,2 weeks,,High-level modeling using whiteboards and paper,High-level modeling using drawing tools,,,Detailed modeling using drawing tools,,,,,,High-level modeling using whiteboards and paper,,,,Detailed modeling using drawing tools,,,,,Detailed estimate based on agile estimation technique,,Fixed price,High-level release plan,,"Yes, the end date is firm due to business need",,,,,,,,We had to show that our stakeholders agreed to the scope,,No
Programmer,10 to 20 years,1 to 10,Technology (inc. Software),Europe,1-2 years,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Team Lead/Scrum Master,20+ years,101 to 500,IT Consulting,North America,3-4 years,10-Jun,The team has daily access to stakeholders,There are many types of stakeholders,Regulatory compliance is an issue,,,,,The team is co-located in a single room,2 weeks,,High-level modeling using whiteboards and paper,,,,,,,Enterprise models used as reference,,,,,,,,,Initial models were provided to us,Enterprise models used as reference,,High-level estimate based on a reasonable guess of experience person(s),,Time and materials,High-level release plan,,"No, we will ship when our stakeholders tell us to",,,,,,,,We had to show that our stakeholders agreed to the scope,,No
Architect,10 to 20 years,1000+,Technology (inc. Software),Australia/NZ,5-10 years,51-100,,There are many types of stakeholders,,,,,,The team is co-located in a single room,4 weeks,No modeling at all,,,,,,,,,,,,,,,,,Initial models were provided to us,,,High-level estimate based on agile estimation technique (e.g. planning poker),,Fixed price,Detailed schedule,,"Yes, we have promised an end date but it may change",,,,,,,,,,No
Other,20+ years,101 to 500,Technology (inc. Software),North America,1-2 years,Don't Know,,There are many types of stakeholders,,This is a mission-critical project,We are evolving an existing legacy system,,,,> 8 weeks,,High-level modeling using whiteboards and paper,,,Detailed modeling using whiteboards and paper,,,,,,,High-level modeling using whiteboards and paper,,,Detailed modeling using whiteboards and paper,,,Initial models were provided to us,,,Detailed estimate based on traditional estimation technique,,Staged-gate funding,No initial project schedule,,"Yes, we have promised an end date but it may change",,We had to estimate the return on investment (ROI),,,,,,,,Yes
Team Lead/Scrum Master,5 to 10 years,51 to 100,Other,North America,< 1 year,10-Jun,,There are many types of stakeholders,,,We are evolving an existing legacy system,Our system accesses legacy data,Our system integrates with legacy systems/components,,5-6 weeks,,High-level modeling using whiteboards and paper,,,,,,,,,,High-level modeling using whiteboards and paper,,,,,,,,,High-level estimate based on agile estimation technique (e.g. planning poker),,Don't know,High-level release plan,,"Yes, the end date is firm due to business need",,We had to estimate the return on investment (ROI),,,,,,We had to show that our stakeholders agreed to the scope,,Don't Know
Programmer,5 to 10 years,51 to 100,Financial,North America,3-4 years,5-Jan,The team has daily access to stakeholders,,Regulatory compliance is an issue,,We are evolving an existing legacy system,Our system accesses legacy data,Our system integrates with legacy systems/components,The team is co-located in a single room,2 weeks,,High-level modeling using whiteboards and paper,,,,,,Initial models were provided to us,,,,High-level modeling using whiteboards and paper,,,,,,,,,High-level estimate based on a reasonable guess of experience person(s),,Don't know,High-level release plan,,"No, we will ship when our stakeholders tell us to",,,,,,,,,legal compliance,Yes
QA/Test,20+ years,101 to 500,IT Consulting,Asia,None,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Team Lead/Scrum Master,20+ years,11 to 50,Technology (inc. Software),North America,5-10 years,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Team Lead/Scrum Master,10 to 20 years,11 to 50,Financial,North America,3-4 years,10-Jun,The team has daily access to stakeholders,There are many types of stakeholders,,,We are evolving an existing legacy system,Our system accesses legacy data,Our system integrates with legacy systems/components,The team is co-located in a single room,Don't know,,,,,,,,,Enterprise models used as reference,Industry models used as reference,,High-level modeling using whiteboards and paper,,,,,,,,,High-level estimate based on a reasonable guess of experience person(s),,Don't know,High-level release plan,,"No, we will ship when our stakeholders tell us to",,,,We had to show that our proposed solution was technically feasible,We had to show that our proposed solution could be supported by our operations group,We had to show that we considered commercial packages,We had to show that we considered offshoring the project,We had to show that our stakeholders agreed to the scope,,No
Team Lead/Scrum Master,20+ years,11 to 50,Financial,North America,5-10 years,10-Jun,,There are many types of stakeholders,Regulatory compliance is an issue,,,,Our system integrates with legacy systems/components,The team is co-located in a single room,2 weeks,,High-level modeling using whiteboards and paper,,,,,,,,,,High-level modeling using whiteboards and paper,High-level modeling using drawing tools,,,,,,,,High-level estimate based on agile estimation technique (e.g. planning poker),,Time and materials,High-level release plan,,"Yes, the end date is firm due to business need",,We had to estimate the return on investment (ROI),,,,,,,,No
Programmer,Less than 2 years,1 to 10,e-Commerce,Asia,None,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Team Lead/Scrum Master,10 to 20 years,1 to 10,Government,North America,1-2 years,10-Jun,The team has daily access to stakeholders,There are many types of stakeholders,Regulatory compliance is an issue,This is a mission-critical project,We are evolving an existing legacy system,Our system accesses legacy data,Our system integrates with legacy systems/components,The team is co-located in a single room,2 weeks,,,,,,Detailed modeling using drawing tools,,,,,,,,,,Detailed modeling using drawing tools,,,,,No initial estimate at all,,Don't know,High-level release plan,,"No, we are still negotiating",,,,We had to show that our proposed solution was technically feasible,,,,,,Yes
Architect,5 to 10 years,1 to 10,Government,North America,1-2 years,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Project Manager,10 to 20 years,51 to 100,e-Commerce,North America,1-2 years,5-Jan,The team has daily access to stakeholders,,Regulatory compliance is an issue,,We are evolving an existing legacy system,,,The team is co-located in a single room,3 weeks,,High-level modeling using whiteboards and paper,,,,,,,,,,High-level modeling using whiteboards and paper,,,,,,,,,High-level estimate based on a reasonable guess of experience person(s),,Time and materials,No initial project schedule,,"No, we are still negotiating",,,,We had to show that our proposed solution was technically feasible,,,,,,Yes
Project Manager,5 to 10 years,11 to 50,Other,South/Central America,1-2 years,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Team Lead/Scrum Master,10 to 20 years,11 to 50,e-Commerce,North America,3-4 years,10-Jun,,There are many types of stakeholders,,,We are evolving an existing legacy system,,,,3 weeks,,,,,,Detailed modeling using drawing tools,,Initial models were provided to us,,,,High-level modeling using whiteboards and paper,,,,,,,,,Detailed estimate based on a reasonable guess of experience person(s),,Don't know,High-level release plan,,"Yes, we have promised an end date but it may change",,,,,,,,,,No
Operations/Support,2 to 5 years,1 to 10,Technology (inc. Software),Europe,< 1 year,5-Jan,,,Regulatory compliance is an issue,,We are evolving an existing legacy system,,,,1 week,No modeling at all,,,,,,,,,,No modeling at all,,,,,,,,,,High-level estimate based on a reasonable guess of experience person(s),,Time and materials,High-level release plan,,"No, we will ship when our stakeholders tell us to",,We had to estimate the return on investment (ROI),,,,,,,,Yes
QA/Test,2 to 5 years,11 to 50,e-Commerce,Asia,1-2 years,20-Nov,The team has daily access to stakeholders,There are many types of stakeholders,Regulatory compliance is an issue,This is a mission-critical project,We are evolving an existing legacy system,Our system accesses legacy data,Our system integrates with legacy systems/components,The team is co-located in a single room,1 week,,High-level modeling using whiteboards and paper,,,,,,,,,,,High-level modeling using drawing tools,,,,,,,,High-level estimate based on a reasonable guess of experience person(s),,Time and materials,High-level release plan,,"Yes, we have promised an end date but it may change",,,,We had to show that our proposed solution was technically feasible,We had to show that our proposed solution could be supported by our operations group,We had to show that we considered commercial packages,,,,Yes
Architect,20+ years,101 to 500,Financial,Europe,< 1 year,21-50,,There are many types of stakeholders,Regulatory compliance is an issue,This is a mission-critical project,,Our system accesses legacy data,Our system integrates with legacy systems/components,The team is co-located in a single room,4 weeks,,High-level modeling using whiteboards and paper,,,,,,,,,,High-level modeling using whiteboards and paper,,,,,,,,,Don't know,,Don't know,Don't know,,"Yes, the end date is firm due to business need",,We had to estimate the return on investment (ROI),,,,,,We had to show that our stakeholders agreed to the scope,,Yes
Team Lead/Scrum Master,5 to 10 years,1000+,Financial,North America,< 1 year,10-Jun,,There are many types of stakeholders,Regulatory compliance is an issue,,,Our system accesses legacy data,Our system integrates with legacy systems/components,,4 weeks,No modeling at all,,,,,,,,,,,High-level modeling using whiteboards and paper,,,,,,Initial models were provided to us,,,High-level estimate based on agile estimation technique (e.g. planning poker),,Staged-gate funding,High-level release plan,,"Yes, we have promised an end date but it may change",,,,,,,,We had to show that our stakeholders agreed to the scope,,Don't Know
IT Manager,10 to 20 years,101 to 500,Financial,North America,5-10 years,21-50,The team has daily access to stakeholders,There are many types of stakeholders,,This is a mission-critical project,,Our system accesses legacy data,Our system integrates with legacy systems/components,,1 week,,High-level modeling using whiteboards and paper,,,,,,Initial models were provided to us,,,,High-level modeling using whiteboards and paper,,,,,,Initial models were provided to us,,,Detailed estimate based on a reasonable guess of experience person(s),,Staged-gate funding,High-level release plan,,"Yes, we have promised an end date but it may change",,,,,,,,We had to show that our stakeholders agreed to the scope,,No
Programmer,20+ years,11 to 50,Technology (inc. Software),Europe,5-10 years,5-Jan,The team has daily access to stakeholders,,,,We are evolving an existing legacy system,,,The team is co-located in a single room,< 1 week,,High-level modeling using whiteboards and paper,,,,,,,,,No modeling at all,,,,,,,,,,High-level estimate based on agile estimation technique (e.g. planning poker),,Staged-gate funding,High-level release plan,,"Yes, the end date is firm due to business need",,,,We had to show that our proposed solution was technically feasible,,,,We had to show that our stakeholders agreed to the scope,,No
Agile Team Member,10 to 20 years,11 to 50,Technology (inc. Software),North America,5-10 years,10-Jun,The team has daily access to stakeholders,,,,We are evolving an existing legacy system,Our system accesses legacy data,Our system integrates with legacy systems/components,,2 weeks,,High-level modeling using whiteboards and paper,,,,,,,,,,High-level modeling using whiteboards and paper,,,,,,,Enterprise models used as reference,,High-level estimate based on agile estimation technique (e.g. planning poker),,Don't know,High-level release plan,,"No, we will ship when our stakeholders tell us to",,,,,We had to show that our proposed solution could be supported by our operations group,,,We had to show that our stakeholders agreed to the scope,,Yes
IT Manager,10 to 20 years,101 to 500,Technology (inc. Software),North America,1-2 years,10-Jun,The team has daily access to stakeholders,There are many types of stakeholders,Regulatory compliance is an issue,This is a mission-critical project,,,Our system integrates with legacy systems/components,,> 8 weeks,,High-level modeling using whiteboards and paper,,,Detailed modeling using whiteboards and paper,,,Initial models were provided to us,Enterprise models used as reference,,,High-level modeling using whiteboards and paper,,,Detailed modeling using whiteboards and paper,,,,Enterprise models used as reference,,No initial estimate at all,,Time and materials,High-level release plan,,"No, we will ship when our stakeholders tell us to",,,We had to estimate the net present value (NPV),We had to show that our proposed solution was technically feasible,We had to show that our proposed solution could be supported by our operations group,,,,,No
Project Manager,20+ years,51 to 100,Technology (inc. Software),North America,3-4 years,51-100,,There are many types of stakeholders,,This is a mission-critical project,We are evolving an existing legacy system,Our system accesses legacy data,Our system integrates with legacy systems/components,,7-8 weeks,,High-level modeling using whiteboards and paper,,,Detailed modeling using whiteboards and paper,,,Initial models were provided to us,,,,High-level modeling using whiteboards and paper,High-level modeling using drawing tools,,Detailed modeling using whiteboards and paper,Detailed modeling using drawing tools,,,,,Detailed estimate based on a reasonable guess of experience person(s),,Fixed price,Detailed schedule,,"Yes, the end date is firm due to business need",,We had to estimate the return on investment (ROI),,We had to show that our proposed solution was technically feasible,We had to show that our proposed solution could be supported by our operations group,,We had to show that we considered offshoring the project,We had to show that our stakeholders agreed to the scope,,Yes
Programmer,5 to 10 years,101 to 500,Technology (inc. Software),Europe,1-2 years,20-Nov,The team has daily access to stakeholders,,,,We are evolving an existing legacy system,,,The team is co-located in a single room,Don't know,,,,,,,,Initial models were provided to us,,,,,,,,,,Initial models were provided to us,,,High-level estimate based on agile estimation technique (e.g. planning poker),,Don't know,High-level release plan,,"Yes, we have promised an end date but it may change",,,,We had to show that our proposed solution was technically feasible,,,,,,Yes
Other,10 to 20 years,101 to 500,Technology (inc. Software),Europe,3-4 years,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Programmer,Less than 2 years,11 to 50,Technology (inc. Software),Europe,1-2 years,10-Jun,The team has daily access to stakeholders,,,This is a mission-critical project,We are evolving an existing legacy system,,,,5-6 weeks,,High-level modeling using whiteboards and paper,,,,,,,Enterprise models used as reference,,,High-level modeling using whiteboards and paper,,,,,,,,,High-level estimate based on agile estimation technique (e.g. planning poker),,Time and materials,High-level release plan,,"Yes, we have promised an end date but it may change",,,,We had to show that our proposed solution was technically feasible,,,,,,No
Programmer,20+ years,1 to 10,Government,Europe,< 1 year,10-Jun,The team has daily access to stakeholders,,,This is a mission-critical project,We are evolving an existing legacy system,,,The team is co-located in a single room,4 weeks,,,,High-level modeling using modeling/CASE tools,,,Detailed modeling using modeling/CASE tools,,,,,,,High-level modeling using modeling/CASE tools,,,Detailed modeling using modeling/CASE tools,,,,High-level estimate based on a reasonable guess of experience person(s),,Time and materials,High-level release plan,,"Yes, the end date is firm due to business need",,,,We had to show that our proposed solution was technically feasible,We had to show that our proposed solution could be supported by our operations group,,,We had to show that our stakeholders agreed to the scope,,Yes
Business Analyst,2 to 5 years,51 to 100,IT Consulting,Europe,3-4 years,10-Jun,The team has daily access to stakeholders,There are many types of stakeholders,,,,Our system accesses legacy data,Our system integrates with legacy systems/components,,3 weeks,,High-level modeling using whiteboards and paper,,High-level modeling using modeling/CASE tools,,Detailed modeling using drawing tools,,Initial models were provided to us,,,,,,,,,,,,Industry models used as reference,Detailed estimate based on a reasonable guess of experience person(s),,Time and materials,High-level release plan,,"Yes, the end date is firm due to business need",,We had to estimate the return on investment (ROI),We had to estimate the net present value (NPV),We had to show that our proposed solution was technically feasible,,,,We had to show that our stakeholders agreed to the scope,,Yes
Programmer,2 to 5 years,11 to 50,Manufacturing,Europe,1-2 years,5-Jan,The team has daily access to stakeholders,There are many types of stakeholders,Regulatory compliance is an issue,,We are evolving an existing legacy system,Our system accesses legacy data,Our system integrates with legacy systems/components,,2 weeks,,High-level modeling using whiteboards and paper,,,,,,,,,No modeling at all,,,,,,,,,,"High-level estimate based on traditional estimation technique (e.g. COCOMO II, Function Points)",,We are still negotiating this,High-level release plan,,"Yes, the end date is firm due to business need",,,,We had to show that our proposed solution was technically feasible,,,,We had to show that our stakeholders agreed to the scope,,No
Architect,20+ years,1 to 10,IT Consulting,North America,> 10 years,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Team Lead/Scrum Master,10 to 20 years,11 to 50,Financial,North America,< 1 year,5-Jan,The team has daily access to stakeholders,,,,,,,,1 week,,High-level modeling using whiteboards and paper,,,,Detailed modeling using drawing tools,,Initial models were provided to us,,,,,,,,,,Initial models were provided to us,,,No initial estimate at all,,Time and materials,High-level release plan,,"No, we are still negotiating",,,,We had to show that our proposed solution was technically feasible,,,,,,No
Architect,10 to 20 years,51 to 100,IT Consulting,North America,1-2 years,21-50,,,,,We are evolving an existing legacy system,,Our system integrates with legacy systems/components,The team is co-located in a single room,Don't know,,High-level modeling using whiteboards and paper,,High-level modeling using modeling/CASE tools,,,,,,,,High-level modeling using whiteboards and paper,,High-level modeling using modeling/CASE tools,,,,,,,High-level estimate based on a reasonable guess of experience person(s),,Fixed price,High-level release plan,,"Yes, the end date is firm due to business need",,,,We had to show that our proposed solution was technically feasible,,,,We had to show that our stakeholders agreed to the scope,,No
Programmer,5 to 10 years,1 to 10,Other,Europe,< 1 year,10-Jun,The team has daily access to stakeholders,,,,,,,The team is co-located in a single room,1 week,,,,,,Detailed modeling using drawing tools,,,,,,,,,,Detailed modeling using drawing tools,,,,,No initial estimate at all,,Fixed price,No initial project schedule,,"Yes, we have promised an end date but it may change",,,,We had to show that our proposed solution was technically feasible,,,,,,No
Other,10 to 20 years,11 to 50,Other,North America,None,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Business Analyst,10 to 20 years,11 to 50,Technology (inc. Software),North America,1-2 years,20-Nov,,There are many types of stakeholders,Regulatory compliance is an issue,,,Our system accesses legacy data,,,3 weeks,,,,,,,Detailed modeling using modeling/CASE tools,,,,,,,High-level modeling using modeling/CASE tools,,,,,,,High-level estimate based on a reasonable guess of experience person(s),,Don't know,High-level release plan,,"No, we are still negotiating",,,,We had to show that our proposed solution was technically feasible,,,,,,No
Project Manager,10 to 20 years,11 to 50,IT Consulting,North America,3-4 years,5-Jan,The team has daily access to stakeholders,,,,,,,The team is co-located in a single room,2 weeks,,,,,,,Detailed modeling using modeling/CASE tools,,,,,,,High-level modeling using modeling/CASE tools,,,,,,,Detailed estimate based on traditional estimation technique,,Time and materials,High-level release plan,,"Yes, we have promised an end date but it may change",,We had to estimate the return on investment (ROI),,,,,,,,Yes
Other,20+ years,501 to 1000,Manufacturing,Europe,5-10 years,10-Jun,The team has daily access to stakeholders,,,,We are evolving an existing legacy system,,Our system integrates with legacy systems/components,,5-6 weeks,,,,,,,Detailed modeling using modeling/CASE tools,,,,,,,,,,Detailed modeling using modeling/CASE tools,,,,Detailed estimate based on agile estimation technique,,Fixed price,High-level release plan,,"Yes, the end date is firm due to business need",,,,We had to show that our proposed solution was technically feasible,,,,,,No
Product Owner,2 to 5 years,11 to 50,Technology (inc. Software),Europe,3-4 years,10-Jun,,There are many types of stakeholders,Regulatory compliance is an issue,This is a mission-critical project,,Our system accesses legacy data,Our system integrates with legacy systems/components,The team is co-located in a single room,> 8 weeks,,High-level modeling using whiteboards and paper,,,,Detailed modeling using drawing tools,,,,,,High-level modeling using whiteboards and paper,,,Detailed modeling using whiteboards and paper,Detailed modeling using drawing tools,,,,,High-level estimate based on a reasonable guess of experience person(s),,Don't know,High-level release plan,,Don't know,We ship every 2 weeks at the end of each sprint. The software is already public. Development is ongoing.,,,,,,,We had to show that our stakeholders agreed to the scope,,No
Other,10 to 20 years,1000+,Technology (inc. Software),North America,1-2 years,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Project Manager,10 to 20 years,101 to 500,Government,Australia/NZ,1-2 years,20-Nov,The team has daily access to stakeholders,There are many types of stakeholders,Regulatory compliance is an issue,This is a mission-critical project,We are evolving an existing legacy system,Our system accesses legacy data,Our system integrates with legacy systems/components,The team is co-located in a single room,4 weeks,,,High-level modeling using drawing tools,,,,,,Enterprise models used as reference,Industry models used as reference,,,High-level modeling using drawing tools,,,,,,Enterprise models used as reference,Industry models used as reference,High-level estimate based on agile estimation technique (e.g. planning poker),,Time and materials,High-level release plan,,"Yes, we have promised an end date but it may change","We have an initial release date that is soft and a project end date that is hard, but with the view that a subset of theteam will stay on and continue on the backlog for at least an additional 18 months.",,,We had to show that our proposed solution was technically feasible,,We had to show that we considered commercial packages,,We had to show that our stakeholders agreed to the scope,,Yes
Project Manager,10 to 20 years,11 to 50,Other,Europe,5-10 years,20-Nov,,,,This is a mission-critical project,We are evolving an existing legacy system,Our system accesses legacy data,Our system integrates with legacy systems/components,,< 1 week,,High-level modeling using whiteboards and paper,,,,,,,,,,High-level modeling using whiteboards and paper,,,,,,,,,High-level estimate based on agile estimation technique (e.g. planning poker),,Time and materials,No initial project schedule,,"No, we will ship when our stakeholders tell us to",,,,We had to show that our proposed solution was technically feasible,We had to show that our proposed solution could be supported by our operations group,,,,,No
Project Manager,5 to 10 years,51 to 100,Technology (inc. Software),Europe,1-2 years,5-Jan,The team has daily access to stakeholders,,,,,,,The team is co-located in a single room,2 weeks,,High-level modeling using whiteboards and paper,,,,,,,,,No modeling at all,,,,,,,,,,Detailed estimate based on agile estimation technique,,Time and materials,High-level release plan,,"Yes, the end date is firm due to business need",,,,,,,,,,No
Team Lead/Scrum Master,5 to 10 years,51 to 100,Other,Europe,3-4 years,5-Jan,The team has daily access to stakeholders,There are many types of stakeholders,,,,,Our system integrates with legacy systems/components,,> 8 weeks,,High-level modeling using whiteboards and paper,,,,,,,,,,High-level modeling using whiteboards and paper,,,,,,,,,High-level estimate based on a reasonable guess of experience person(s),,Fixed price,High-level release plan,,"Yes, we have promised an end date but it may change",,We had to estimate the return on investment (ROI),,,,We had to show that we considered commercial packages,,We had to show that our stakeholders agreed to the scope,,Yes
Team Lead/Scrum Master,2 to 5 years,11 to 50,Technology (inc. Software),Europe,< 1 year,5-Jan,The team has daily access to stakeholders,There are many types of stakeholders,,,We are evolving an existing legacy system,,Our system integrates with legacy systems/components,The team is co-located in a single room,1 week,No modeling at all,High-level modeling using whiteboards and paper,,,,,,,,,No modeling at all,High-level modeling using whiteboards and paper,,,,,,,,,High-level estimate based on agile estimation technique (e.g. planning poker),,Fixed price,High-level release plan,,"Yes, the end date is firm due to business need",,,,,,,,,"We inherited an existing project and ""restarted"" development using Agile. Contracts were already in place.",Yes
Team Lead/Scrum Master,20+ years,11 to 50,Technology (inc. Software),Europe,3-4 years,10-Jun,The team has daily access to stakeholders,There are many types of stakeholders,Regulatory compliance is an issue,This is a mission-critical project,We are evolving an existing legacy system,Our system accesses legacy data,Our system integrates with legacy systems/components,The team is co-located in a single room,5-6 weeks,,High-level modeling using whiteboards and paper,,,,,,,,Industry models used as reference,,High-level modeling using whiteboards and paper,,,,,,,,,High-level estimate based on a reasonable guess of experience person(s),,Time and materials with delivery bonus(s),Detailed schedule,,"Yes, the end date is firm due to business need",,We had to estimate the return on investment (ROI),We had to estimate the net present value (NPV),,,,We had to show that we considered offshoring the project,We had to show that our stakeholders agreed to the scope,,Yes
Programmer,10 to 20 years,11 to 50,Technology (inc. Software),Europe,1-2 years,10-Jun,,There are many types of stakeholders,,This is a mission-critical project,We are evolving an existing legacy system,Our system accesses legacy data,Our system integrates with legacy systems/components,The team is co-located in a single room,3 weeks,,High-level modeling using whiteboards and paper,,,Detailed modeling using whiteboards and paper,,,,,,,High-level modeling using whiteboards and paper,,,Detailed modeling using whiteboards and paper,,,,,,High-level estimate based on agile estimation technique (e.g. planning poker),,Staged-gate funding,High-level release plan,,"Yes, the end date is firm due to business need",,,,We had to show that our proposed solution was technically feasible,We had to show that our proposed solution could be supported by our operations group,,We had to show that we considered offshoring the project,We had to show that our stakeholders agreed to the scope,,No
Project Manager,10 to 20 years,11 to 50,Government,Europe,5-10 years,20-Nov,The team has daily access to stakeholders,,Regulatory compliance is an issue,This is a mission-critical project,,Our system accesses legacy data,Our system integrates with legacy systems/components,The team is co-located in a single room,7-8 weeks,,High-level modeling using whiteboards and paper,,High-level modeling using modeling/CASE tools,,,,,,,,High-level modeling using whiteboards and paper,,High-level modeling using modeling/CASE tools,,,,,,,High-level estimate based on a reasonable guess of experience person(s),,Staged-gate funding,High-level release plan,,"Yes, we have promised an end date but it may change",,,,,,,,We had to show that our stakeholders agreed to the scope,,Yes
IT Manager,20+ years,51 to 100,Financial,South/Central America,3-4 years,10-Jun,The team has daily access to stakeholders,There are many types of stakeholders,,This is a mission-critical project,We are evolving an existing legacy system,,,The team is co-located in a single room,4 weeks,,,High-level modeling using drawing tools,,,,,,,,,,High-level modeling using drawing tools,,,,,,Enterprise models used as reference,,"High-level estimate based on traditional estimation technique (e.g. COCOMO II, Function Points)",,Time and materials,High-level release plan,,"Yes, we have promised an end date but it may change",,,,,,,,,,Yes
Other,10 to 20 years,51 to 100,Other,Europe,5-10 years,10-Jun,,There are many types of stakeholders,,,,Our system accesses legacy data,Our system integrates with legacy systems/components,The team is co-located in a single room,5-6 weeks,,High-level modeling using whiteboards and paper,,,,,,,,,,,,,Detailed modeling using whiteboards and paper,,,,,,High-level estimate based on agile estimation technique (e.g. planning poker),,We are still negotiating this,High-level release plan,,"Yes, the end date is firm due to business need",,,,We had to show that our proposed solution was technically feasible,We had to show that our proposed solution could be supported by our operations group,,,We had to show that our stakeholders agreed to the scope,,Yes
Team Lead/Scrum Master,10 to 20 years,1000+,Financial,Europe,5-10 years,10-Jun,The team has daily access to stakeholders,There are many types of stakeholders,Regulatory compliance is an issue,This is a mission-critical project,,Our system accesses legacy data,Our system integrates with legacy systems/components,,4 weeks,No modeling at all,,,,,,,,,,,High-level modeling using whiteboards and paper,,,,,,,,,High-level estimate based on agile estimation technique (e.g. planning poker),,Time and materials,High-level release plan,,"Yes, the end date is firm due to legislation",,,,,,,,,,No
Team Lead/Scrum Master,20+ years,1 to 10,IT Consulting,Europe,< 1 year,5-Jan,The team has daily access to stakeholders,,,,We are evolving an existing legacy system,,Our system integrates with legacy systems/components,,3 weeks,,High-level modeling using whiteboards and paper,,,,,,,,,,High-level modeling using whiteboards and paper,,,,,,,,,High-level estimate based on a reasonable guess of experience person(s),,Fixed price,High-level release plan,,"No, we will ship when our stakeholders tell us to",,,,We had to show that our proposed solution was technically feasible,,,,We had to show that our stakeholders agreed to the scope,,No
Other,5 to 10 years,1000+,Technology (inc. Software),Europe,3-4 years,20-Nov,The team has daily access to stakeholders,There are many types of stakeholders,Regulatory compliance is an issue,,,,,,Don't know,,High-level modeling using whiteboards and paper,High-level modeling using drawing tools,,Detailed modeling using whiteboards and paper,Detailed modeling using drawing tools,,Initial models were provided to us,,,,High-level modeling using whiteboards and paper,High-level modeling using drawing tools,,Detailed modeling using whiteboards and paper,Detailed modeling using drawing tools,,Initial models were provided to us,,,High-level estimate based on a reasonable guess of experience person(s),,Fixed price,High-level release plan,,"Yes, we have promised an end date but it may change",,We had to estimate the return on investment (ROI),,We had to show that our proposed solution was technically feasible,,We had to show that we considered commercial packages,We had to show that we considered offshoring the project,We had to show that our stakeholders agreed to the scope,,Yes
Other,10 to 20 years,101 to 500,IT Consulting,Europe,5-10 years,10-Jun,The team has daily access to stakeholders,There are many types of stakeholders,,,,,,,4 weeks,,High-level modeling using whiteboards and paper,,,,,,,,,,High-level modeling using whiteboards and paper,,,,,,,,,High-level estimate based on agile estimation technique (e.g. planning poker),,Staged-gate funding,High-level release plan,,"Yes, the end date is firm due to business need",,,,We had to show that our proposed solution was technically feasible,We had to show that our proposed solution could be supported by our operations group,We had to show that we considered commercial packages,,We had to show that our stakeholders agreed to the scope,,Yes
Team Lead/Scrum Master,20+ years,11 to 50,Technology (inc. Software),North America,1-2 years,10-Jun,The team has daily access to stakeholders,There are many types of stakeholders,Regulatory compliance is an issue,This is a mission-critical project,,,,,5-6 weeks,,High-level modeling using whiteboards and paper,High-level modeling using drawing tools,,Detailed modeling using whiteboards and paper,Detailed modeling using drawing tools,,Initial models were provided to us,,,,High-level modeling using whiteboards and paper,High-level modeling using drawing tools,,Detailed modeling using whiteboards and paper,Detailed modeling using drawing tools,,Initial models were provided to us,,,High-level estimate based on a reasonable guess of experience person(s),,Staged-gate funding,High-level release plan,,"Yes, the end date is firm due to business need",,We had to estimate the return on investment (ROI),,We had to show that our proposed solution was technically feasible,We had to show that our proposed solution could be supported by our operations group,,,We had to show that our stakeholders agreed to the scope,,Yes
Project Manager,5 to 10 years,101 to 500,Technology (inc. Software),Asia,3-4 years,21-50,The team has daily access to stakeholders,There are many types of stakeholders,,,We are evolving an existing legacy system,,Our system integrates with legacy systems/components,,4 weeks,,High-level modeling using whiteboards and paper,High-level modeling using drawing tools,,,,,,,,,,High-level modeling using drawing tools,,,,,,,,High-level estimate based on a reasonable guess of experience person(s),,Time and materials,High-level release plan,,"No, we are still negotiating",,We had to estimate the return on investment (ROI),,,,,,,,No
Team Lead/Scrum Master,5 to 10 years,101 to 500,Technology (inc. Software),Asia,< 1 year,10-Jun,,There are many types of stakeholders,,This is a mission-critical project,,Our system accesses legacy data,,The team is co-located in a single room,4 weeks,,,,,,Detailed modeling using drawing tools,,,,,,,High-level modeling using drawing tools,,,,,,,,"High-level estimate based on traditional estimation technique (e.g. COCOMO II, Function Points)",,Fixed price,High-level release plan,,"Yes, the end date is firm due to business need",,We had to estimate the return on investment (ROI),,,,,,We had to show that our stakeholders agreed to the scope,,No
IT Manager,5 to 10 years,1000+,IT Consulting,Europe,None,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Project Manager,5 to 10 years,1 to 10,Other,Asia,1-2 years,5-Jan,The team has daily access to stakeholders,,,,,,,,2 weeks,,,,High-level modeling using modeling/CASE tools,,,,,,Industry models used as reference,,,,High-level modeling using modeling/CASE tools,,,,,,Industry models used as reference,High-level estimate based on agile estimation technique (e.g. planning poker),,Don't know,High-level release plan,,"Yes, we have promised an end date but it may change",,,,,,,,,,Yes
Team Lead/Scrum Master,2 to 5 years,11 to 50,Technology (inc. Software),Asia,3-4 years,10-Jun,The team has daily access to stakeholders,,,,,,,The team is co-located in a single room,1 week,,High-level modeling using whiteboards and paper,High-level modeling using drawing tools,,,,,,,Industry models used as reference,,High-level modeling using whiteboards and paper,High-level modeling using drawing tools,,,,,,,Industry models used as reference,High-level estimate based on a reasonable guess of experience person(s),,Time and materials,Detailed schedule,,"Yes, we have promised an end date but it may change",We ship every sprint after the 1st release unless it is blocked by client,,,We had to show that our proposed solution was technically feasible,We had to show that our proposed solution could be supported by our operations group,,We had to show that we considered offshoring the project,,,Yes
Architect,10 to 20 years,51 to 100,e-Commerce,North America,< 1 year,10-Jun,The team has daily access to stakeholders,There are many types of stakeholders,,,We are evolving an existing legacy system,,,The team is co-located in a single room,5-6 weeks,,,,High-level modeling using modeling/CASE tools,,,,,,,,,,High-level modeling using modeling/CASE tools,,,,,,,Detailed estimate based on a reasonable guess of experience person(s),,Don't know,Detailed schedule,,"Yes, the end date is firm due to business need",,,,We had to show that our proposed solution was technically feasible,,,,We had to show that our stakeholders agreed to the scope,,Yes
Other,5 to 10 years,11 to 50,Technology (inc. Software),Asia,5-10 years,51-100,,There are many types of stakeholders,,,We are evolving an existing legacy system,,,,< 1 week,,High-level modeling using whiteboards and paper,,High-level modeling using modeling/CASE tools,,,,,,,,High-level modeling using whiteboards and paper,,,,,,,Enterprise models used as reference,,Detailed estimate based on agile estimation technique,,Don't know,High-level release plan,,"Yes, the end date is firm due to business need",,,,,,,,,,No
Architect,10 to 20 years,51 to 100,Technology (inc. Software),North America,3-4 years,51-100,,,,This is a mission-critical project,,Our system accesses legacy data,,,4 weeks,,High-level modeling using whiteboards and paper,High-level modeling using drawing tools,,,,,,,,,High-level modeling using whiteboards and paper,High-level modeling using drawing tools,,Detailed modeling using whiteboards and paper,Detailed modeling using drawing tools,,,,,"High-level estimate based on traditional estimation technique (e.g. COCOMO II, Function Points)",,Time and materials,Detailed schedule,,"Yes, the end date is firm due to business need",,We had to estimate the return on investment (ROI),,We had to show that our proposed solution was technically feasible,We had to show that our proposed solution could be supported by our operations group,,,We had to show that our stakeholders agreed to the scope,,Yes
IT Manager,20+ years,1 to 10,Technology (inc. Software),North America,5-10 years,5-Jan,The team has daily access to stakeholders,There are many types of stakeholders,,,,,,The team is co-located in a single room,3 weeks,,High-level modeling using whiteboards and paper,,,,,,,,,,High-level modeling using whiteboards and paper,High-level modeling using drawing tools,,,,,,,,High-level estimate based on agile estimation technique (e.g. planning poker),,Staged-gate funding,High-level release plan,,"No, we will ship when our stakeholders tell us to",,,,,,,,,,Yes
Architect,20+ years,1 to 10,IT Consulting,North America,< 1 year,5-Jan,The team has daily access to stakeholders,,,,We are evolving an existing legacy system,,Our system integrates with legacy systems/components,The team is co-located in a single room,5-6 weeks,,,High-level modeling using drawing tools,,,,,,,Industry models used as reference,,,High-level modeling using drawing tools,,,,,,,Industry models used as reference,No initial estimate at all,,We are still negotiating this,High-level release plan,,Don't know,We are slated to maintain and enhance on an ongoing basis.,,,We had to show that our proposed solution was technically feasible,,We had to show that we considered commercial packages,,We had to show that our stakeholders agreed to the scope,,No
Business Analyst,5 to 10 years,51 to 100,Financial,Europe,1-2 years,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Programmer,10 to 20 years,1000+,IT Consulting,North America,3-4 years,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Agile Team Member,None,1 to 10,e-Commerce,North America,1-2 years,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Team Lead/Scrum Master,20+ years,101 to 500,Technology (inc. Software),North America,5-10 years,21-50,The team has daily access to stakeholders,There are many types of stakeholders,,,,Our system accesses legacy data,Our system integrates with legacy systems/components,The team is co-located in a single room,Don't know,,High-level modeling using whiteboards and paper,,,,,,,,,,High-level modeling using whiteboards and paper,,,Detailed modeling using whiteboards and paper,,,,,,High-level estimate based on agile estimation technique (e.g. planning poker),,Don't know,High-level release plan,,"Yes, the end date is firm due to business need",,,,We had to show that our proposed solution was technically feasible,,,,,,No
Programmer,10 to 20 years,1000+,Other,North America,1-2 years,10-Jun,,,,,We are evolving an existing legacy system,,,,4 weeks,,,,High-level modeling using modeling/CASE tools,,,,,,,,,High-level modeling using drawing tools,,,,,,,,High-level estimate based on a reasonable guess of experience person(s),,Time and materials,Detailed schedule,,"Yes, the end date is firm due to business need",,,,,,,,We had to show that our stakeholders agreed to the scope,,Yes
Other,20+ years,1 to 10,IT Consulting,Europe,> 10 years,21-50,The team has daily access to stakeholders,There are many types of stakeholders,Regulatory compliance is an issue,This is a mission-critical project,We are evolving an existing legacy system,Our system accesses legacy data,Our system integrates with legacy systems/components,,4 weeks,,High-level modeling using whiteboards and paper,,,,,,,,,,High-level modeling using whiteboards and paper,,,,,,,,,High-level estimate based on a reasonable guess of experience person(s),,Staged-gate funding,High-level release plan,,"Yes, the end date is firm due to business need",,,,We had to show that our proposed solution was technically feasible,We had to show that our proposed solution could be supported by our operations group,,,We had to show that our stakeholders agreed to the scope,,Yes
Project Manager,20+ years,51 to 100,Other,North America,5-10 years,21-50,,There are many types of stakeholders,Regulatory compliance is an issue,This is a mission-critical project,,Our system accesses legacy data,Our system integrates with legacy systems/components,,3 weeks,,High-level modeling using whiteboards and paper,,,Detailed modeling using whiteboards and paper,Detailed modeling using drawing tools,,,,Industry models used as reference,,High-level modeling using whiteboards and paper,,,Detailed modeling using whiteboards and paper,Detailed modeling using drawing tools,,,,Industry models used as reference,Detailed estimate based on agile estimation technique,,Staged-gate funding,High-level release plan,,"Yes, we have promised an end date but it may change",,We had to estimate the return on investment (ROI),We had to estimate the net present value (NPV),We had to show that our proposed solution was technically feasible,We had to show that our proposed solution could be supported by our operations group,We had to show that we considered commercial packages,,We had to show that our stakeholders agreed to the scope,,Yes
Product Owner,10 to 20 years,1 to 10,Other,North America,3-4 years,5-Jan,The team has daily access to stakeholders,There are many types of stakeholders,,,,Our system accesses legacy data,Our system integrates with legacy systems/components,The team is co-located in a single room,1 week,,,High-level modeling using drawing tools,,,,,,,,,,High-level modeling using drawing tools,,,,,,,,Detailed estimate based on a reasonable guess of experience person(s),,Don't know,High-level release plan,,"Yes, the end date is firm due to business need",,,,,,,,We had to show that our stakeholders agreed to the scope,,Yes
Team Lead/Scrum Master,20+ years,1 to 10,Technology (inc. Software),North America,5-10 years,10-Jun,The team has daily access to stakeholders,There are many types of stakeholders,,,We are evolving an existing legacy system,Our system accesses legacy data,Our system integrates with legacy systems/components,,4 weeks,,High-level modeling using whiteboards and paper,,High-level modeling using modeling/CASE tools,,,Detailed modeling using modeling/CASE tools,,,,,High-level modeling using whiteboards and paper,High-level modeling using drawing tools,High-level modeling using modeling/CASE tools,,,,,,,No initial estimate at all,,Time and materials,High-level release plan,,"Yes, the end date is firm due to business need",,,,We had to show that our proposed solution was technically feasible,,We had to show that we considered commercial packages,,We had to show that our stakeholders agreed to the scope,,No
IT Manager,10 to 20 years,11 to 50,Other,North America,3-4 years,10-Jun,The team has daily access to stakeholders,,,This is a mission-critical project,We are evolving an existing legacy system,Our system accesses legacy data,Our system integrates with legacy systems/components,The team is co-located in a single room,2 weeks,,High-level modeling using whiteboards and paper,High-level modeling using drawing tools,,,,,,Enterprise models used as reference,,,High-level modeling using whiteboards and paper,High-level modeling using drawing tools,,,,,,Enterprise models used as reference,,High-level estimate based on a reasonable guess of experience person(s),,Time and materials,High-level release plan,,"Yes, we have promised an end date but it may change",,,,,,,,,We were driven to accomplish due to technical changes to up stream data feeds.,No
Team Lead/Scrum Master,20+ years,11 to 50,Technology (inc. Software),Europe,1-2 years,5-Jan,The team has daily access to stakeholders,,,,,,,The team is co-located in a single room,1 week,,High-level modeling using whiteboards and paper,,,,,,,,,,High-level modeling using whiteboards and paper,,,,,,,,,High-level estimate based on agile estimation technique (e.g. planning poker),,Fixed price,High-level release plan,,"Yes, we have promised an end date but it may change",,We had to estimate the return on investment (ROI),,,,,,,,Yes
IT Manager,20+ years,11 to 50,e-Commerce,North America,3-4 years,5-Jan,The team has daily access to stakeholders,There are many types of stakeholders,,,,Our system accesses legacy data,,,> 8 weeks,No modeling at all,,,,,,,,,,No modeling at all,,,,,,,,,,High-level estimate based on a reasonable guess of experience person(s),,Staged-gate funding,High-level release plan,,"No, we will ship when our stakeholders tell us to",,,,,,,,,no,Yes
Project Manager,5 to 10 years,51 to 100,Manufacturing,Europe,None,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Architect,20+ years,51 to 100,Technology (inc. Software),North America,3-4 years,5-Jan,The team has daily access to stakeholders,,,,,Our system accesses legacy data,Our system integrates with legacy systems/components,,< 1 week,,High-level modeling using whiteboards and paper,,,Detailed modeling using whiteboards and paper,,,,,Industry models used as reference,,High-level modeling using whiteboards and paper,,,,,,,,,High-level estimate based on a reasonable guess of experience person(s),,Time and materials,High-level release plan,,"No, we will ship when our stakeholders tell us to",,,,We had to show that our proposed solution was technically feasible,We had to show that our proposed solution could be supported by our operations group,,,,,No
Team Lead/Scrum Master,20+ years,11 to 50,Technology (inc. Software),North America,5-10 years,5-Jan,The team has daily access to stakeholders,There are many types of stakeholders,Regulatory compliance is an issue,This is a mission-critical project,We are evolving an existing legacy system,,Our system integrates with legacy systems/components,The team is co-located in a single room,5-6 weeks,,High-level modeling using whiteboards and paper,High-level modeling using drawing tools,,,,,,Enterprise models used as reference,,,High-level modeling using whiteboards and paper,High-level modeling using drawing tools,,,,,,Enterprise models used as reference,Industry models used as reference,High-level estimate based on a reasonable guess of experience person(s),,Staged-gate funding,High-level release plan,,"Yes, we have promised an end date but it may change",,We had to estimate the return on investment (ROI),,We had to show that our proposed solution was technically feasible,,,,,,Yes
Team Lead/Scrum Master,20+ years,1 to 10,IT Consulting,North America,5-10 years,10-Jun,The team has daily access to stakeholders,There are many types of stakeholders,,This is a mission-critical project,We are evolving an existing legacy system,Our system accesses legacy data,Our system integrates with legacy systems/components,The team is co-located in a single room,1 week,,High-level modeling using whiteboards and paper,,,,,,Initial models were provided to us,,,,High-level modeling using whiteboards and paper,,,,,,,,,High-level estimate based on a reasonable guess of experience person(s),,Time and materials,High-level release plan,"High-level release plan, finite sprint deadline/sprint backlog planning for individual sprints","Yes, the end date is firm due to business need",,,,We had to show that our proposed solution was technically feasible,,We had to show that we considered commercial packages,,We had to show that our stakeholders agreed to the scope,,Yes
Team Lead/Scrum Master,10 to 20 years,51 to 100,Technology (inc. Software),North America,1-2 years,20-Nov,,,Regulatory compliance is an issue,,We are evolving an existing legacy system,Our system accesses legacy data,Our system integrates with legacy systems/components,The team is co-located in a single room,> 8 weeks,,High-level modeling using whiteboards and paper,High-level modeling using drawing tools,,,,,,,Industry models used as reference,,High-level modeling using whiteboards and paper,High-level modeling using drawing tools,,,,,,,Industry models used as reference,High-level estimate based on a reasonable guess of experience person(s),,Staged-gate funding,Detailed schedule,,"Yes, the end date is firm due to business need",,We had to estimate the return on investment (ROI),,We had to show that our proposed solution was technically feasible,We had to show that our proposed solution could be supported by our operations group,,We had to show that we considered offshoring the project,We had to show that our stakeholders agreed to the scope,,Yes
Team Lead/Scrum Master,2 to 5 years,101 to 500,Financial,North America,1-2 years,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Team Lead/Scrum Master,5 to 10 years,11 to 50,Technology (inc. Software),Asia,3-4 years,10-Jun,,There are many types of stakeholders,,This is a mission-critical project,We are evolving an existing legacy system,Our system accesses legacy data,,,> 8 weeks,,High-level modeling using whiteboards and paper,,High-level modeling using modeling/CASE tools,Detailed modeling using whiteboards and paper,,Detailed modeling using modeling/CASE tools,Initial models were provided to us,,Industry models used as reference,,,,High-level modeling using modeling/CASE tools,,,Detailed modeling using modeling/CASE tools,,,Industry models used as reference,High-level estimate based on a reasonable guess of experience person(s),,Time and materials with delivery bonus(s),Detailed schedule,,"Yes, the end date is firm due to business need",,,,,,We had to show that we considered commercial packages,We had to show that we considered offshoring the project,,,No
Programmer,Less than 2 years,1000+,Technology (inc. Software),North America,None,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Team Lead/Scrum Master,10 to 20 years,11 to 50,Manufacturing,North America,None,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Programmer,10 to 20 years,11 to 50,Technology (inc. Software),Europe,3-4 years,5-Jan,The team has daily access to stakeholders,There are many types of stakeholders,,,We are evolving an existing legacy system,,,,Don't know,No modeling at all,,,,,,,,,,,,,,,,,,Enterprise models used as reference,,Detailed estimate based on traditional estimation technique,,Don't know,High-level release plan,,"Yes, the end date is firm due to business need",,,,,,,,,,No
Architect,10 to 20 years,51 to 100,Government,North America,3-4 years,10-Jun,,There are many types of stakeholders,Regulatory compliance is an issue,This is a mission-critical project,,Our system accesses legacy data,,,4 weeks,,High-level modeling using whiteboards and paper,,,,,,,,,,High-level modeling using whiteboards and paper,,,Detailed modeling using whiteboards and paper,,,,,,High-level estimate based on a reasonable guess of experience person(s),,Fixed price,High-level release plan,schedule pre-determined,"Yes, the end date is firm due to business need",,,,We had to show that our proposed solution was technically feasible,We had to show that our proposed solution could be supported by our operations group,,,We had to show that our stakeholders agreed to the scope,,Yes
Architect,20+ years,11 to 50,Technology (inc. Software),North America,5-10 years,10-Jun,The team has daily access to stakeholders,There are many types of stakeholders,Regulatory compliance is an issue,This is a mission-critical project,We are evolving an existing legacy system,Our system accesses legacy data,Our system integrates with legacy systems/components,The team is co-located in a single room,4 weeks,,High-level modeling using whiteboards and paper,,,,,,,,,,High-level modeling using whiteboards and paper,,,Detailed modeling using whiteboards and paper,,,,,,High-level estimate based on a reasonable guess of experience person(s),,Time and materials,High-level release plan,,"No, we will ship when our stakeholders tell us to",,We had to estimate the return on investment (ROI),,We had to show that our proposed solution was technically feasible,We had to show that our proposed solution could be supported by our operations group,We had to show that we considered commercial packages,,,,Yes
Agile Team Member,10 to 20 years,501 to 1000,Technology (inc. Software),North America,< 1 year,10-Jun,,There are many types of stakeholders,Regulatory compliance is an issue,This is a mission-critical project,We are evolving an existing legacy system,,,,5-6 weeks,,High-level modeling using whiteboards and paper,,High-level modeling using modeling/CASE tools,,,,,,,,,,,,,,Initial models were provided to us,,,Don't know,This was accomplished prior to me joining the team.,Don't know,Detailed schedule,,"Yes, the end date is firm due to business need",,,,We had to show that our proposed solution was technically feasible,,,,,,No
Programmer,5 to 10 years,1 to 10,Manufacturing,North America,< 1 year,5-Jan,The team has daily access to stakeholders,,,,We are evolving an existing legacy system,Our system accesses legacy data,Our system integrates with legacy systems/components,The team is co-located in a single room,3 weeks,,,,,,,,Initial models were provided to us,,,,,,,,,,Initial models were provided to us,,,High-level estimate based on a reasonable guess of experience person(s),,Fixed price,Don't know,,"Yes, we have promised an end date but it may change",,,,,,,,,,No
Team Lead/Scrum Master,5 to 10 years,1 to 10,Technology (inc. Software),North America,< 1 year,5-Jan,The team has daily access to stakeholders,There are many types of stakeholders,,,We are evolving an existing legacy system,,,The team is co-located in a single room,< 1 week,,High-level modeling using whiteboards and paper,,,,,,,,,,High-level modeling using whiteboards and paper,,,,,,,,,High-level estimate based on agile estimation technique (e.g. planning poker),,Don't know,High-level release plan,,"No, we are still negotiating",,,,,,,,,,No
Team Lead/Scrum Master,10 to 20 years,11 to 50,Technology (inc. Software),North America,< 1 year,10-Jun,The team has daily access to stakeholders,There are many types of stakeholders,Regulatory compliance is an issue,,We are evolving an existing legacy system,Our system accesses legacy data,Our system integrates with legacy systems/components,The team is co-located in a single room,4 weeks,,High-level modeling using whiteboards and paper,High-level modeling using drawing tools,,,,,,,,,High-level modeling using whiteboards and paper,,,,,,,,,High-level estimate based on agile estimation technique (e.g. planning poker),,Staged-gate funding,High-level release plan,,"Yes, the end date is firm due to business need",,We had to estimate the return on investment (ROI),,,,,,,,Yes
Team Lead/Scrum Master,10 to 20 years,11 to 50,Technology (inc. Software),Europe,5-10 years,10-Jun,The team has daily access to stakeholders,,,This is a mission-critical project,,Our system accesses legacy data,Our system integrates with legacy systems/components,The team is co-located in a single room,> 8 weeks,,,,,,,,Initial models were provided to us,,,,,High-level modeling using drawing tools,,,Detailed modeling using drawing tools,,,,,Detailed estimate based on agile estimation technique,,Don't know,High-level release plan,,"Yes, the end date is firm due to business need",,,,We had to show that our proposed solution was technically feasible,We had to show that our proposed solution could be supported by our operations group,,,,,Don't Know
Team Lead/Scrum Master,2 to 5 years,1000+,Technology (inc. Software),North America,3-4 years,21-50,The team has daily access to stakeholders,,,,,,,,5-6 weeks,,High-level modeling using whiteboards and paper,,High-level modeling using modeling/CASE tools,,,,,,,,High-level modeling using whiteboards and paper,,High-level modeling using modeling/CASE tools,,,,,,,High-level estimate based on agile estimation technique (e.g. planning poker),,Don't know,Detailed schedule,,"Yes, the end date is firm due to business need",,,,We had to show that our proposed solution was technically feasible,,,,,,Yes
Project Manager,10 to 20 years,51 to 100,IT Consulting,North America,5-10 years,21-50,The team has daily access to stakeholders,There are many types of stakeholders,Regulatory compliance is an issue,This is a mission-critical project,,,,,2 weeks,,High-level modeling using whiteboards and paper,,,,,,,,,,High-level modeling using whiteboards and paper,,,,,,,,,No initial estimate at all,I was brought in after the start of the project - if I were here we would have done a planning poker session,Time and materials with delivery bonus(s),High-level release plan,,"Yes, the end date is firm due to business need",,,,,,,,,None - we were hired by client to delvier product,Yes
Agile Team Member,5 to 10 years,1 to 10,Government,North America,3-4 years,5-Jan,The team has daily access to stakeholders,There are many types of stakeholders,,This is a mission-critical project,,Our system accesses legacy data,Our system integrates with legacy systems/components,The team is co-located in a single room,Don't know,,High-level modeling using whiteboards and paper,,,,,,,,,,High-level modeling using whiteboards and paper,,,,,,,,Industry models used as reference,High-level estimate based on agile estimation technique (e.g. planning poker),,Don't know,High-level release plan,,"No, we will ship when our stakeholders tell us to",,We had to estimate the return on investment (ROI),,,,We had to show that we considered commercial packages,,We had to show that our stakeholders agreed to the scope,,Don't Know
Programmer,10 to 20 years,11 to 50,Technology (inc. Software),North America,1-2 years,20-Nov,,There are many types of stakeholders,,,We are evolving an existing legacy system,,Our system integrates with legacy systems/components,,4 weeks,,,,,,,,Initial models were provided to us,,,,,,,,,,Initial models were provided to us,,,High-level estimate based on agile estimation technique (e.g. planning poker),,Don't know,High-level release plan,,"Yes, the end date is firm due to business need",,We had to estimate the return on investment (ROI),,,,,,,,No
Programmer,5 to 10 years,1 to 10,IT Consulting,North America,5-10 years,20-Nov,,There are many types of stakeholders,,This is a mission-critical project,We are evolving an existing legacy system,Our system accesses legacy data,Our system integrates with legacy systems/components,,Don't know,No modeling at all,,,,,,,,,,No modeling at all,,,,,,,,,,Don't know,,Fixed price,High-level release plan,,"Yes, the end date is firm due to business need",,,,We had to show that our proposed solution was technically feasible,,,,,,Yes
Project Manager,20+ years,11 to 50,Technology (inc. Software),North America,< 1 year,5-Jan,,There are many types of stakeholders,,,,,Our system integrates with legacy systems/components,The team is co-located in a single room,3 weeks,,,High-level modeling using drawing tools,,,Detailed modeling using drawing tools,,Initial models were provided to us,,,,High-level modeling using whiteboards and paper,,,,,,,,,High-level estimate based on a reasonable guess of experience person(s),,We are still negotiating this,High-level release plan,,"No, we are still negotiating",,We had to estimate the return on investment (ROI),,,,,,,,No
Architect,5 to 10 years,51 to 100,Financial,Europe,3-4 years,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Other,10 to 20 years,1000+,Technology (inc. Software),North America,5-10 years,10-Jun,,There are many types of stakeholders,Regulatory compliance is an issue,,,,Our system integrates with legacy systems/components,,2 weeks,,High-level modeling using whiteboards and paper,,,,,,Initial models were provided to us,Enterprise models used as reference,Industry models used as reference,,High-level modeling using whiteboards and paper,,,,,,Initial models were provided to us,Enterprise models used as reference,,High-level estimate based on agile estimation technique (e.g. planning poker),,Time and materials,High-level release plan,,"Yes, the end date is firm due to business need",,We had to estimate the return on investment (ROI),,,,,,We had to show that our stakeholders agreed to the scope,,Yes
Team Lead/Scrum Master,5 to 10 years,51 to 100,Technology (inc. Software),Europe,3-4 years,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Project Manager,20+ years,101 to 500,Manufacturing,North America,None,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Business Analyst,10 to 20 years,1 to 10,Technology (inc. Software),North America,< 1 year,10-Jun,The team has daily access to stakeholders,,,,,,,The team is co-located in a single room,< 1 week,,High-level modeling using whiteboards and paper,,,Detailed modeling using whiteboards and paper,,,,,,No modeling at all,,,,,,,,,,High-level estimate based on agile estimation technique (e.g. planning poker),,Don't know,High-level release plan,,"Yes, the end date is firm due to business need",,,,,,,,,,No
Other,20+ years,11 to 50,Other,North America,5-10 years,5-Jan,The team has daily access to stakeholders,There are many types of stakeholders,,,,,Our system integrates with legacy systems/components,The team is co-located in a single room,3 weeks,,High-level modeling using whiteboards and paper,,,Detailed modeling using whiteboards and paper,,,,,,,High-level modeling using whiteboards and paper,,,,,,,,,High-level estimate based on agile estimation technique (e.g. planning poker),,Time and materials,No initial project schedule,,"No, we will ship when our stakeholders tell us to",,,,We had to show that our proposed solution was technically feasible,,,,,,No
Architect,10 to 20 years,51 to 100,IT Consulting,Europe,3-4 years,10-Jun,,There are many types of stakeholders,Regulatory compliance is an issue,This is a mission-critical project,,Our system accesses legacy data,,,Don't know,,,,,,,Detailed modeling using modeling/CASE tools,,,,,,,,,,Detailed modeling using modeling/CASE tools,,,,Detailed estimate based on traditional estimation technique,,Fixed price,Detailed schedule,,"Yes, the end date is firm due to legislation",,,We had to estimate the net present value (NPV),,,,,,,No
Agile Team Member,Less than 2 years,1 to 10,Technology (inc. Software),South/Central America,< 1 year,10-Jun,,There are many types of stakeholders,Regulatory compliance is an issue,,,Our system accesses legacy data,,The team is co-located in a single room,5-6 weeks,,,,,Detailed modeling using whiteboards and paper,,,Initial models were provided to us,,,,,,High-level modeling using modeling/CASE tools,Detailed modeling using whiteboards and paper,,,,,Industry models used as reference,Detailed estimate based on a reasonable guess of experience person(s),,Fixed price,High-level release plan,,"Yes, the end date is firm due to business need",,,,,We had to show that our proposed solution could be supported by our operations group,,,,,Yes
Other,10 to 20 years,501 to 1000,Technology (inc. Software),Europe,5-10 years,51-100,,There are many types of stakeholders,,,,,Our system integrates with legacy systems/components,,3 weeks,,High-level modeling using whiteboards and paper,,,,,,,Enterprise models used as reference,Industry models used as reference,,High-level modeling using whiteboards and paper,,,,,,,Enterprise models used as reference,Industry models used as reference,High-level estimate based on a reasonable guess of experience person(s),,Staged-gate funding,High-level release plan,,"Yes, the end date is firm due to business need",,We had to estimate the return on investment (ROI),,We had to show that our proposed solution was technically feasible,We had to show that our proposed solution could be supported by our operations group,We had to show that we considered commercial packages,We had to show that we considered offshoring the project,We had to show that our stakeholders agreed to the scope,,Yes
Programmer,2 to 5 years,1 to 10,IT Consulting,Europe,< 1 year,5-Jan,The team has daily access to stakeholders,There are many types of stakeholders,,This is a mission-critical project,,Our system accesses legacy data,Our system integrates with legacy systems/components,The team is co-located in a single room,2 weeks,,High-level modeling using whiteboards and paper,,,,,,,,,,High-level modeling using whiteboards and paper,High-level modeling using drawing tools,,,,,,,,High-level estimate based on a reasonable guess of experience person(s),,Fixed price,High-level release plan,,"Yes, the end date is firm due to business need",,We had to estimate the return on investment (ROI),We had to estimate the net present value (NPV),We had to show that our proposed solution was technically feasible,We had to show that our proposed solution could be supported by our operations group,,,We had to show that our stakeholders agreed to the scope,,Don't Know
IT Manager,10 to 20 years,11 to 50,Technology (inc. Software),South/Central America,5-10 years,5-Jan,The team has daily access to stakeholders,There are many types of stakeholders,,,,,,The team is co-located in a single room,2 weeks,,High-level modeling using whiteboards and paper,,,,,,,,,,High-level modeling using whiteboards and paper,,,,,,,,,"High-level estimate based on traditional estimation technique (e.g. COCOMO II, Function Points)",,Fixed price,High-level release plan,,"Yes, the end date is firm due to business need",,We had to estimate the return on investment (ROI),,,,,,,,Yes
Architect,20+ years,101 to 500,Financial,North America,> 10 years,21-50,The team has daily access to stakeholders,There are many types of stakeholders,Regulatory compliance is an issue,This is a mission-critical project,We are evolving an existing legacy system,Our system accesses legacy data,Our system integrates with legacy systems/components,,3 weeks,,High-level modeling using whiteboards and paper,High-level modeling using drawing tools,,,,,,,,,High-level modeling using whiteboards and paper,High-level modeling using drawing tools,,,,,,,,High-level estimate based on a reasonable guess of experience person(s),,Time and materials,High-level release plan,,"Yes, we have promised an end date but it may change",,,,We had to show that our proposed solution was technically feasible,,,,We had to show that our stakeholders agreed to the scope,,Yes
Team Lead/Scrum Master,20+ years,101 to 500,Government,North America,1-2 years,5-Jan,,There are many types of stakeholders,,,,,,The team is co-located in a single room,2 weeks,,,,High-level modeling using modeling/CASE tools,,,,,Enterprise models used as reference,,,,,,,,,Initial models were provided to us,,,High-level estimate based on agile estimation technique (e.g. planning poker),,Time and materials,High-level release plan,,"Yes, the end date is firm due to business need",,,,We had to show that our proposed solution was technically feasible,,,,We had to show that our stakeholders agreed to the scope,,Yes
Other,20+ years,51 to 100,e-Commerce,North America,5-10 years,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Programmer,5 to 10 years,11 to 50,Shipping,North America,1-2 years,5-Jan,The team has daily access to stakeholders,There are many types of stakeholders,,,,,,The team is co-located in a single room,Don't know,,High-level modeling using whiteboards and paper,,,,,,,,,,,High-level modeling using drawing tools,,,,,,,,High-level estimate based on a reasonable guess of experience person(s),,Don't know,High-level release plan,,"Yes, we have promised an end date but it may change",,,,We had to show that our proposed solution was technically feasible,,,,We had to show that our stakeholders agreed to the scope,,No
Team Lead/Scrum Master,10 to 20 years,1000+,Financial,North America,3-4 years,10-Jun,The team has daily access to stakeholders,There are many types of stakeholders,Regulatory compliance is an issue,,We are evolving an existing legacy system,Our system accesses legacy data,Our system integrates with legacy systems/components,The team is co-located in a single room,4 weeks,,High-level modeling using whiteboards and paper,,,,,,,,,,,,,,,,,Enterprise models used as reference,,High-level estimate based on a reasonable guess of experience person(s),,Fixed price,High-level release plan,,"Yes, we have promised an end date but it may change",,We had to estimate the return on investment (ROI),,,,,,,,Yes
Programmer,2 to 5 years,101 to 500,Financial,North America,1-2 years,5-Jan,,There are many types of stakeholders,,,We are evolving an existing legacy system,,Our system integrates with legacy systems/components,,4 weeks,,High-level modeling using whiteboards and paper,,,Detailed modeling using whiteboards and paper,,,,,,,High-level modeling using whiteboards and paper,High-level modeling using drawing tools,,,,,,,,High-level estimate based on a reasonable guess of experience person(s),,Don't know,High-level release plan,,"No, we are still negotiating",,,,,We had to show that our proposed solution could be supported by our operations group,We had to show that we considered commercial packages,,We had to show that our stakeholders agreed to the scope,,Yes
Business Stakeholder,20+ years,11 to 50,Technology (inc. Software),Europe,None,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,