K EY Q UESTIONS AND T AKE A WAYS 87

CloudTeams should drive its professional users more towards the “product manager” concept, where users have a complete overview of the product, including customers, market characteris- tics, clients, but also technical issues, tasks and architectures. This multi-disciplinary should be cultivated and promoted through the CloudTeams tools.

In the following table there is an aggregated version of the questions emerged during the SotA analysis in this document. As a next step, this table will be circulated as a separate document to the consortium and will be part of the discussion in the Athens project meeting in June 2015; the results of this “brainstorming” exercise will be documented in D1.3.

Table 8. 75 questions for the CloudTeams consortium

Location in the document Questions

Chapter 2: Software Development 2.1 Software Engineering Methodologies 2.1.1.Software development process

76.  What kinds of software development activities are sup- ported by the CloudTeams platform?

77.  What are the input and the output of these activities? 78.  Can a process be adapted/changed after a project has

started?

79.  What kinds of metrics are used to measure progress and quality within a project?

80.  What kinds of roles are necessary to maintain commu- nity activities?

2.1.2. User par- ticipation

81.  How could incentivize users migrate into agile devel- opment processes?

82.  What activities could be supported by user communi- ties and what are the artefacts needed?

83.  How is the quality of external artefacts monitored and if necessary improved?

2.2. Team Col- laboration

2.2.1. IDEs 84.  In which extend shall CloudTeams provide an IDE? 85.  If there is an IDE, what collaborative features shall it

support in CloudTeams?

86.  Is there any open source project ready to be integrated? 2.2.2 Code Re-

positories 87.  Which code repositories are supported? _{88.  Shall CloudTeams promote or encourage open sourced} projects and incentivize teams to contribute back to the community?

Location in the document Questions

89.  Shall CloudTeams support sharing knowledge and code among teams participating in the platform? E.g. libraries, architectures, best practices, libraries of gen- eral personas, etc.

90.  Shall CloudTeams code parts be also given as open source? What license?

91.  Shall open sourcing CloudTeams give transparency to the project on how data are used?

2.2.3. Build Au- tomation Solu- tions

92.  Which build automation tools are supported? 93.  Can CloudTeams support both Maven and Gradle? 94.  Can current generation of build automation tools be

exploited for social collaboration? 2.2.4. Automat-

ed Deployment –continuous integration

95.  Which Build Automation and Continuous Integration software can be used?

96.  Which social collaboration endpoints of the selected solution will be used?

97.  Are notification mechanisms offered by Continuous Integration tools sufficient for CloudTeams?

2.2.5. Code Quality Review

98.  Which Code Quality review software can be used? 99.  Will CloudTeams use notifications for informing users

for possible code quality related events?

100.   What events will trigger the notifications to be sent? 2.2.6. Artifact

repository

101.   Which artifact repository can be used?

102.   Can artifact sharing be considered enough for social collaboration in CloudTeams?

103.   Can CloudTeams provide any more social capabili- ties related to artifact repository?

2.2.7.Bug

Tracking 104.   Which bug tracking software shall be connected _{with CloudTeams?} 2.2.8. Conclu-

sions on team- collaboration software life cycle

105.   Does CloudTeams implement a specific develop- ment cycle

106.   Does CloudTeams provide collaboration and social abilities to all points of a development cycle?

Location in the document Questions

capsulated in CloudTeams?

108.   Are the collaboration and social abilities of the se- lected tools sufficient?

2.3. Popular PaaS Platforms 109.   Does CloudTeams need to support both private and public PaaS platforms?

110.   Does CloudTeams support multiple PaaS platforms? 111.   Which PaaS platforms will be supported?

112.   Will the interoperability functionalities offered by Cloud4SOA, PaaSport or other projects be used? 2.4 Product Management Methodologies 2.4.1. Software Management Methodologies

113.   Does CloudTeams support a management method- ology or develops its own?

114.   Could CloudTeams combine the three trending and dominant methods (Lean Startup, Business Model Generation and Design Thinking)?

115.   To which extend can CloudTeams claim a “la- bel/verification” for supporting specific methodolo- gies?

2.4.2. Product Management Tools

116.   Does CloudTeams develop its own product man- agement tools or reuses some of the suggested/known tools?

117.   Are developers allowed to create their own analytics or does CloudTeams provide fixed solutions for their needs?

2.4.3. Team Collaboration Tools

118.   Shall CloudTeams provide an API on its own? 119.   Shall CloudTeams consume APIs from existing plat-

forms or build features from scratch?

120.   Which services should be integrated? In which pri- ority?

121.   Shall CloudTeams take into consideration UX and usability improvements? E.g. mobile access?

3. Early Adopters Community Engagement

3.1. Crowdsourcing platforms 122.   Experts (open innovation), regular users (ideation) or mix (hybrid)?

123.   Materialized rewards or incentives of participation? 124.   Integration with existing platforms for data analysis?

Location in the document Questions

125.   Should CloudTeams enable users under contests with prizes (i.e. trigger competition among partici- pants)? 3.2. Social Collaboration in Software Lifecycle 3.2.1 Software

Development 126.   Which elicitation techniques shall CloudTeams sup-_port? 127.   Shall CloudTeams support any requirements specifi-

cation standard?

128.   Shall CloudTeams support an existing requirement capturing framework or develop a new one?

129.   Shall CloudTeams track SotA technologies/best practices and practices by experts to produce technical requirements or focus only on user requirements? 130.   Shall CloudTeams provide automated, system sup-

ported or developer/product manager-driven process for extracting requirements?

131.   Which mockup tools CloudTeams is possible to use? 132.   What social collaboration functionalities

CloudTeams want to offer?

133.   Are existing open source mock-up tools sufficient of there is need to develop a new one?

134.   Which bug tracking software will be used?

135.   What kind of social collaboration will be provided by CloudTeams?

3.2.2 Social Characteristics in Software Support

136.   Shall CloudTeams define/ filter profile characteris- tics of experts to take part in the crowdsourced V&V process and in what way?

137.   Shall CloudTeams provide a method/tool supporting the coordination of the crowdsourced V&V process? 138.   Should CloudTeams be able to integrate with all ex-

isting crowd testing platforms?

139.   In what way CloudTeams shall handle trust and pri- vacy issues in crowd-sourced V&V activities?

140.   What type of documentation CloudTeams envision to offer?

141.   What tools will CloudTeams support?

142.   Should CloudTeams provide support for text docu- mentation for deployed projects?

Location in the document Questions

143.   Should CloudTeams provide support for video based documentation for deployed projects?

144.   Shall CloudTeams support generation of supporting content?

145.   What content shall CloudTeams integrate in project descriptions in order to make them more clear and un- derstandable to early adopters?

146.   Shall CloudTeams offer a forum to support every project?

3.3. Growth Hack Techniques:

User engagement & gamification 147.   Will CloudTeams support aggregation of activities, _{will it provide interface to become another registry for} human activities, or will it follow a hybrid approach? 148.   Does CloudTeams and software teams consider data

coming from sensors more reliable, or do they ask for a variety of resources?

149.   Shall CloudTeams develop both a rewarding and a gamification mechanism, or choose between them? 150.   Will CloudTeams develop its own gamification en-

gine from scratch, will it use an external platform or will it use existing libraries?

It shall be the responsibility of this task to inform the rest of the consortium for the results of this document. These questions alone cover all the important or minor issues that the CloudTeams design and development consortium should take into consideration; it is also a brief manual for everyone that should clarify what CloudTeams does and what does not. Apart from these ques- tions, this document has provided a detailed analysis in methodologies (e.g. software engineer- ing, software innovation management, crowdsourcing, gamification, requirements etc.), which will be taken into consideration in Task 1.2 and generate the CloudTeams concepts in Delivera- ble 1.3. Additionally, this task collaborated in depth with Task 1.3 to generate a concrete plan, for workflows and needs in data, in order to get early feedback by board of ethics, as well as build a solid privacy framework.