Workshop it! is the time saving digital solution which help to store all the information on the server to avoid losing some ideas written on post-it stickers. That is why Workshop it! has replaced brown paper with a digitize one, displayed by a projector and post-it papers by tablets or phones for each participant.

1. Master of Science in Informatics at Grenoble
Workshop it!
Problem Solving Team Building Digital Solution
Supervisor
Fran¸cois Delaunay, Agnes Front
Candidate
Shweta Agrawal
September 1, 2016

2. Outline
• Presentation of Enterprise & Workshop it!
• Overview
• Problem Statement & Proposed Solution
• Contributions
• Testing and it’s results
• Conclusions and Future Work
2 of 38

3. Presentation of Enterprise
• Extellient is a service based company located in Grenoble
• Established in 2005
• Directed by Fran¸cois Delaunay and Patrick Torrents
• Offers consulting, software engineering and technical assistance
• Offer full support to create mobile applications
• Its own product is Workshop it!
• Prefered technologies are JAVA, PHP5, HTML5, CSS3,
JavaScript
3 of 38

4. Presentation of Workshop it!
• It is the time saving digital solution
• Used for collaborative workshops to improve ideas and to make
better decisions
• Remote user can also attend the workshop
• Used in training, meeting, seminar and events
Figure: Low tech to High tech graphics
4 of 38

5. What is PSTB?
• Stands for Problem Solving Team Building
• Workshop it! brings PSTB to your digital devices
• It is an efficient means of running a meeting to find a solution to
an open, intractable issue by using the collective intelligence of
the team
• Basically it uses a large brown paper taped to the meeting room
wall, Post-It notes, markers and other goodies handed out to the
participants.
5 of 38

6. PSTB user involvement
It is made up of different categories of people:
• Facilitator
• Clients
• Users
6 of 38

7. System Environment
Figure: System Environment
7 of 38

8. Overview: Initial Scenarios
• Initializing a client space and managing first user accounts
• Preparing a workshop
• Getting the mobile App to participate in a workshop
• Workshop runtime
• After workshop
Figure: Workshop Life Cycle
8 of 38

9. Overview: Detailed scenario of PSTB workshop
• Steps 1 and 2: brief stage - Problem statement and context
• Step 3: Idea generation
• Step 4: Idea selection
• Steps 5 and 6: Benefits and concerns, killer concern
• Step 7: Action plan
Figure: Ideas Life Cycle
9 of 38

10. Problem Statement & Proposed Solution
• Problem1: Manually send user guides to individual is an
unbearable condition for the company.
10 of 38

11. Problem Statement & Proposed Solution
• Problem1: Manually send user guides to individual is an
unbearable condition for the company.
Solution: Private support system would consider the best solution
11 of 38

12. Problem Statement & Proposed Solution
• Problem1: Manually send user guides to individual is an
unbearable condition for the company.
Solution: Private support system would consider the best solution
• Problem2: As it is consider each workshop as an independent
issue, so there is a no way to link multiple workshops for final
objective
12 of 38

13. Problem Statement & Proposed Solution
• Problem1: Manually send user guides to individual is an
unbearable condition for the company.
Solution: Private support system would consider the best solution
• Problem2: As it is consider each workshop as an independent
issue, so there is a no way to link multiple workshops for final
objective
Solution: Program Management is the solution where owner
manage multiple workshops and their dependency
13 of 38

14. Resource Center
Needs: Several user guides are available and it cannot afford this
unbearable situation to send manual guides.
Objective: Main goal is to make available user guides to
authenticated users only within the application.
14 of 38

15. Resource Center Specification
Front end specifications: Display list of resources according visibility
conditions that have been defined by super administrator for each of
them.
Possible visibility conditions are:
• restricted or not to ”not free trial” plans
• restricted or not to Administrator profile
Figure: Help and Support 15 of 38

16. Resource Center Document
Back end specifications: Enable super administrator to manage
resource center, upload documents in different languages and upload
updates.
Figure: Resource Center Document List
16 of 38

17. Resource Center Releases
Figure is showing all the available version of participant’s user guide
Figure: Resource Center Document’s Releases
17 of 38

18. Program Management-Needs
Workshop it! considers each workshop as an independent issue. The
Program Management functionality had fulfilled the need for
organizing a ”program”, it means a set of workshops aiming at a
final objective.
Figure: UML diagram for existing and new entities
18 of 38

19. Program Management-Specifications
• Create, list, update and delete are the basic features of program
• Program view display page:
◦ show program general properties
◦ list user groups
◦ list workshops
◦ workshop timeline, show their dependencies and their status
◦ display some simple graphical objects that monitors completion /
progress
• Workgroup Management
• Workshop Management
19 of 38

20. Program View
Figure: Program detailed view 20 of 38

21. Workgroup Management
A workgroup is defined within the scope of a given program and for
its sole usage.
Figure: Workgroup List
21 of 38

22. Workgroup Users
Add/Remove users in workgroup within the program
Figure: Add users in workgroup
22 of 38

23. Workshop Management
Program responsible can declare workshops as belonging to its
program and one workshop can not belong to another program
Figure: Workshop list 23 of 38

24. Workshop’s Workgroup
Adding and removing workgroups in the worshop is a two way data
binding. When you add or remove workgroup from workshop, it will
reflect on the workshop list as well as on timeline
Figure: Add/remove workgroup in workshop
24 of 38

25. Workshop Workgroup dependency
Program responsible can add/retrieve one or more workgroups
to/from a workshop.
Figure: Gantt chart for workshops and their dependencies
25 of 38

26. Workshop State
Workshop’s state bar chart which is showing the progress of total
number of workshop state (created/open/close) within the program
Figure: Progress bar for workshop’s state
26 of 38

27. Workshop’s Idea state
Workshop idea’s state bar chart which is showing the total number
of ideas states (shared/dismissed/selected) of workshop have been
taken into account
Figure: Stacked bar chart for idea’s state of workshop
27 of 38

28. Technologies and Tools used
• Technologies: Symfony2, AngularJs, HTML, CSS
• Tools: Virtual machine, PHP Storm, Putty
28 of 38

29. Contribution
→ Proposing ideas
→ Draw technical specifications
→ Design and Development
→ Testing and Verification
29 of 38

30. Unit Testing
The goal of unit testing is to isolate each part of the program and
show that the individual parts are correct.
• PHP unit testing: It is used to test all the methods and services
defined for backend functionality
• Angular unit testing: It is used to test methods defined for
frontend functionality
30 of 38

31. PHP Unit Test: Pseudo code
#Unit Test to check the "Create Program" Service
public function testCreateProgramSuccess() {
$customer = // get customer object by companyname
$user = // get user object by user id
$program = new ProgramFormObject();
$program->title = ’MoSiG Program’;
$program->description = ’International Master Program’;
$program->start_date = // insert start date
$program->end_date = //insert end date >= start date
$result =
$this->getProgramService()->createProgram($program,
$user, $customer);
$this->assertEquals(1, count($result),"program is
registered successfully"); 31 of 38

32. PHP Unit Test: Result
Results of all services of program:
PHPUnit 4.8.26 by Sebastian Bergmann and contributors.
Time: 24.62 seconds, Memory: 94.00MB
OK (8 tests, 52 assertions)
32 of 38

33. AngularJS Pseudo code
#ProgramController.js
angular.module(’programApp’, []);
angular.module(’programApp’)
.controller(’programCtrl’, [’$scope’, function($scope) {
$scope.workshops = []; // define workshop array
//add workshop func
$scope.addWorkshop = function (workshop) {
$scope.workshops.push(workshop);
};
//remove workshop func
$scope.removeWorkshop = function (i) {
$scope.workshops.splice(i);
};
}]); 33 of 38

34. Angular Unit Test: Pseudo code
#ProgramControllerTests.js
describe(’The Workshop Controller’, function(){
var scope;
beforeEach(module(’workshopApp’));
beforeEach(inject(function ($rootScope, $controller) {
......
}));
describe(’when we add a workshop’, function () {
......
assert.equal(scope.workshops[0].name, ’1st workshop’);
});
describe(’when we remove a workshop’, function () {
......
assert.ok(!scope.workshops.length);
}); 34 of 38

35. Angular Unit Test: Result
karma start
......
PhantomJS 2.1.1 (Linux 0.0.0): Executed 2 of 2 SUCCESS (0.041
secs / 0 secs)
35 of 38

36. Conclusion
• Workshop it! Digitised Problem Solving / Team Building
• Brainstorming meeting to generate ideas
• Keep timing under control
• Outcomes are shared instantly on-line and can be downloaded.
• Cross entity participation is possible for the workshop planned by
a given entity involves facilitator, owner or participants of other
entities
36 of 38

37. Future Work
• I-Calendar invitations and attendees list
• Workshop type other than PSTB
• Workgroup Uses
37 of 38

38. Thank you for your attention!
38 of 38