1. Management Processes Application Bc. Ľubomír Kaplán, Bc. Martin Janočko, Bc. Andrej Mlynčár, Bc. Lukáš Kleščinec, Bc. Tomáš Hermánek, Bc. Tomáš Mikuška 8.12.2015 1

2. Risk Management Identification Analysis Planning Control Responsible: Bc. Tomáš Hermánek Standards established Risk Definition Standards Risk Handling Standards 2

3. Risk Management – Risk Attributes Risk name Description Probability – low, medium, high Impact – low, medium, high, critical Trigger Prevention Consequences Solution 3

4. Risk Management (1) Absence of a team member on a meeting Impact: Low Probability: Medium Trigger: Unexpected events can happen and team member is not able to attend team meeting 4

5. Risk Management (2) Team member is not able to finish a task. Impact: Medium Probability: Medium Trigger: Task estimation was set incorrectly. Bad time management from team member. Unexpected events can happen (sickness, school/work deadlines). 5

6. Risk Management (3) Impossible to finish working prototype or documentation. Impact: Critical Probability: Low Trigger: Bad time management, low effort 6

7. Communication Management Responsible: Bc. Martin Janočko Standards established Means of Communication Communication Standards 7

8. Means of Communication JIRA Confluence Email Social Media Personal 8

9. Communication Standards (1) JIRA Tasks Issues Comments Reviews Confluence Documents Knowledge Base Specifications 9

10. Communication Standards (2) Email Communication with Team Leader Group Mailing List Social Media Informal Communication Meetings Planning Personal Team Meetings 10

11. Documentation and Storage Management Responsible: Bc. Lukáš Kleščinec Standards established Documentation Standards Document Storage Standard 11

12. Document Storage Standards Separate spaces Public documentation NetCell Documentation Private documentation NetCell Development 12

13. Public Documentation – NetCell Documentation Space User manuals and guidelines Contains: Node Type Development Node Type Configuration Definition 13

14. Private Documentation – NetCell Development Project Proposal Project Team Cloud Environment and VPN Access NetCell Logos NetCell Node Client NetCell Management Server Useful links 14

15. Documentation Standards (1) Documentation standards created at the beginning of WS 2 Types of documentation: Guidelines, manuals created with new tool/functionality TP course documentation Based on course definition Special task in JIRA – approval on team meeting Based on internal template – occasionally unfulfilled “In review“ status helps to detect most of mistakes 15

16. Documentation Standards (2) Developer Manuals Installation guidelines Prerequisites How use tool– all switches etc. Stored into confluence TP documentation/user manuals Approval on team meeting Create task in JIRA for each sub-section 16

17. Quality Management Responsible: Andrej Mlynčár Standards established Code Review Standards Coding Standards Issue Tracker & Issue Linking Standards 17

18. Code Review Created JIRA Board with “In Review” Status Every task was reviewed Quality Manager takes responsibility for assigning tasks for review Everyone took part in task/issue review 18

19. Coding Standards Coding Standards created at the beginning of WS Two separated standards – python & java Defined variable names, code formatting… Reviewed as a part of code review. 19

20. Issue Tracker & Linking JIRA Issue tracker Project VNET Used standard issue types and workflow Linking not often used – caused by lack of experience with JIRA 20

21. Development Management Responsible: Bc. Ľubomír Kaplán Standards established Backlog Standards Story Point Standards Version Control Standards 21

22. Backlog Standards Created on team meetings Everyone participated on backlog creation Story point estimation 22

23. Story Point Standards Fibonacci series-based story points Team members casted their vote for story point amount for every issue at the same time Value repeated the most in the voting was used 23

24. Version Control Standards (1) Git repositories GitLab as SCM Multiple projects As minimum number of changes per commit as possible Issue names in front of commits for bug fixing 24

25. Version Control Standards (2) Management Server Common Libraries and Utilities Node Type Client Projects 25

26. Test Management Responsible: Bc. Tomáš Mikuška Standards established: Testing Standards – Unit, Integration, System,... 26

27. Testing Life Cycle Establish objectives Design Write Test Execute Evaluate results 27

28. Unit Testing Test each method individually Error handling White-box testing Done by developers 28

29. Integration Testing Integration Testing Framework (PAX) Node Configuration Tools 29

30. System Testing Acceptance testing Topology Template Management Topology Deployment Group Configuration Management Performance testing Not accessible Usability testing 30

31. Thank you for your attention! VirtNET Team virtnet@castor.sk http://virtnet.castor.sk 31