Cloudteams Playbook
Total Page：16
File Type：pdf, Size：1020Kb
CloudTeams Playbook A guide for Product Managers in Software Development supported by the CloudTeams Platform Version 1, February 2017 www.CloudTeams.eu The CloudTeams Playbook Disclaimer: This e-book is published under the project CloudTeams, co-funded by the European Commission, under the Horizon 2020 funding scheme (Grant Agreement No: 644617). Under this project, different partners from Fraunhofer Institute for Applied Information Technology FIT, National Technical University of Athens (NTUA), Singular Logic (SILO), FZI, Booreiland (BOOR) and YASAD came together in order to realize the CloudTeams platform and validate the CloudTeams methodology, as developed in the project. In this document, as authors and editors are considered the persons that actively participated in the production of the current document solely, without forgetting the important role and contribution of every partner involved in the project, individually. Project Partners: FIT (DE), NTUA (GR), FZI (DE), SILO (GR), YASAD (TR), BOOR (NL) Every effort has been made to ensure that all statements and information contained herein are accurate, however the Partners accept no liability for any error or omission in the same. This project has received funding from The European Union's Framework Programme for Research and Innovation - Horizon 2020, under Grant Agreement No: 644617. Action full title: 'Collaborative Software Development Framework based on Trusted, Secure Cloud-based Pool of Users'. ICT-07-2014: Advanced Cloud Infrastructures and Services 2 The CloudTeams Playbook This book is available under Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) You are free to: Share — copy and redistribute the material in any medium or format Adapt — remix, transform, and build upon the material for any purpose, even commercially. The licensor cannot revoke these freedoms as long as you follow the license terms. Under the following terms: Attribution — You must give appropriate credit, provide a link to the license, and indicate if changes were made. You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use. ShareAlike — If you remix, transform, or build upon the material, you must distribute your contributions under the same license as the original. No additional restrictions — You may not apply legal terms or technological measures that legally restrict others from doing anything the license permits. Notices: You do not have to comply with the license for elements of the material in the public domain or where your use is permitted by an applicable exception or limitation. No warranties are given. The license may not give you all of the permissions necessary for your intended use. For example, other rights such as publicity, privacy, or moral rights may limit how you use the material. 3 The CloudTeams Playbook Main Authors & Contributors Main author Iosif Alvertis MSc in Electrical & Computer Engineering, National Technical University of Athens (NTUA), Greece MBA in Entrepreneurship & Innovation, Athens University of Economics & Business, Greece PhD Candidate in Electrical & Computer Engineering, NTUA, Greece Emails: [email protected], [email protected] Decision Support Systems Laboratory, NTUA, Greece Main Contributors Giannis Ledakis, Dipl. Eng. Software Engineer, CEID University of Patras, Greece [email protected] SingularLogic S.A. Dimitris Panopoulos, Dr. MSc in Mechanical Engineering, National Technical University of Athens (NTUA), Greece MBA in Technoeconomic Systems, NTUA & University of Piraeus, Greece PhD in Electrical & Computer Engineering, NTUA, Greece Emails: [email protected], [email protected] Decision Support Systems Laboratory, NTUA, Greece Editor Sotiris Koussouris, Dr. MSc in Electrical & Computer Engineering, National Technical University of Athens (NTUA), Greece MBA in Technoeconomic Systems, NTUA & University of Piraeus, Greece PhD in IT Business Process Modelling and Re-engineering, School of Electrical & Computer Engineering, NTUA, Greece Email: [email protected] Decision Support Systems Laboratory, NTUA, Greece Illustrated by Iosif Alvertis Booreiland Strategic Interaction Design Email: [email protected] Website: http://booreiland.nl/ 4 The CloudTeams Playbook Table of Contents 1 Introduction 8 2 What a Product Manager is 9 3 The CloudTeams Methodology 10 4 The CloudTeams Platform 14 5 Running the CloudTeams methodology step by step 17 5.1 Step 1: Ideation & Idea validation 17 5.2 Step 2: User Experience & Scenarios Validation 23 5.3 Step 3: System Backlog Definition & User Stories Validation 31 5.4 Step 4: Sprint Backlog Definition 38 5.5 Step 5: Design and Visual Modelling 40 5.6 Step 6: Coding 44 5.7 Step 7: Automated Unit Testing 46 5.8 Step 8: Continuous Integration Testing 47 5.9 Step 9: Automated Acceptance Testing 49 5.10 Step 10: Regression & Functional Testing 50 5.11 Step 11: User Acceptance Testing – UAT 54 5.12 Step 12: Market Test 58 6 Summary 61 5 The CloudTeams Playbook Table of Figures Figure 3-1. The ideation and idea validation as visualized in the CloudTeams methodology 10 Figure 3-2. The CloudTeams methodology expanded with an Agile Software Development methodology 11 Figure 3-3. Using CloudTeams Methodology under different Software Engineering Methodologies 13 Figure 4-1. The general architecture of the CloudTeams platform 14 Figure 4-2. The main offerings of the CloudTeams platform for Software Teams (left sidebar) 15 Figure 4-3. The CloudTeams Personas as a layer of Privacy to enable CloudTeams campaigns 16 Figure 5-1. The ideation and idea validation as visualized in the CloudTeams methodology 17 Figure 5-2. Step 1 - Ideation & Idea Validation workflow 18 Figure 5-3. Documenting Business Model Canvases in CloudTeams Platform 20 Figure 5-4. The user experience and scenarios validation as visualized in the CloudTeams methodology 24 Figure 5-5. Step 2 - User Experience & Scenarios Validation workflow 24 Figure 5-6. The System Backlog Definition and User Stories Validation steps, as visualized in the CloudTeams methodology 32 Figure 5-7. System backlog definition and User Stories Validation 33 Figure 5-8. Hierarchy in User Stories, relation with the goal of each level, and relative examples 34 Figure 5-9. Putting the user stories in priority 35 Figure 5-10. An example of a workflow that completes an interaction (i.e. a user map) 36 Figure 5-11. CloudTeams Platform allows the documentation of both Scenarios and User Stories 37 Figure 5-12. The position of Step 4 (Sprint Backlog Definition) in the implementation phase 39 Figure 5-13. Connecting external services to a CloudTeams project 40 Figure 5-14. The complete diagram of Step 4 “Design and Visual Modelling” 41 Figure 5-15. The “Snape” application helps software teams manage their UML diagrams 44 Figure 5-16. Suggestion on Product Manager engagement in Code Collaboration through CloudTeams 46 Figure 5-18. Suggested workflow for Continuous Integration and Automated Deployment 49 Figure 5-20. The relation of step 10 (regression and functional testing) with step 3 (system backlog definition and update) 51 Figure 5-21. The suggested workflow for regression and functional testing 52 Figure 5-22. The relation of step 11 (user acceptance testing) with step 2 (user experience) 54 Figure 5-23. Running the User Acceptance Testing. 55 Figure 5-24. Setting up a UEQ (or other) questionnaire through CloudTeams platform 57 Figure 5-25. Validating the product based on market tests 58 Figure 5-26. Running the “final” step of the Market Test 59 6 The CloudTeams Playbook Table of Tables Table 5-1. The criteria based on which an idea should be evaluated (i.e. first column), related to the business where the ideas lay, interrelated based on the level of importance. N/A=important, *=very important, **=extremely important 22 Table 5-2. The criteria based on which an idea should be evaluated (rows), related to the business where the ideas lays, interrelated based on the level of importance (columns). N/I= not important (low), *= important (medium), **=very important (high) 27 Table 5-3. Relation of strategies and criteria’s score (at least reaching the suggested score) 28 Table 5-4. Well-known User Acceptance Testing models 30 Table 5-5. An example of documenting a Use Case 37 Table 5-6. 7. The software development cycle in Software Development, Testi ng and Verification 45 Table 5-8. The template for unsupervised use case auditing (evaluating use cases) 52 Table 5-9. Different metrics for running supervised testing 53 Table 5-10. Comparing well-known evaluation frameworks where partners are experienced in 55 Table 5-11. Evaluation Metrics selected for the CloudTeams Pilots Operation 56 7 The CloudTeams Playbook 1 Introduction This Playbook combines best practices described in various guides and methodologies, in order to deliver a handbook for every Product Manager (PM), a series of steps that should follow in order to increase the chances of launching a successful software product. This handbook is accompanied with real-life scenarios that our team faced during the development phase of CloudTeams itself, and showcases the techniques we used to meet our goals. Nevertheless, the innovation that this Playbook brings is that it is accompanied by a web tool, the CloudTeams platform, which is designed to support the PM throughout different steps of the product development phase; this is the reason it is called a “Playbook” and not a “Handbook”, as it brings a playground for PMs to apply the theory, with a great level of flexibility and customization. This Playbook should be read and mastered by people working as Product Managers, or people who want to become ones. However, it is expected to be shared with the team members, as well as with high levels of management, in order to help an organization to align its goals under a common mentality. The team that applies this Playbook may declared itself as “rigid”, “agile” or “lean”, but it may use parts or complete steps of the methodology and tools of the platform.