Application Specific Computing. Project Organization. A. Kugel, Projects

Transcription

1 Application Specific Computing Project Organization 1

2 Slides and Resources 2

3 PTG Wrap-Up Lessons learned (if you actually did PTG ) Start early => finish early is a lie if W > 1 Little s law: L = W / λ Makes Little s law worse! Parallel work (L : lead time, W: work items, λ: throughput) Overhead on human multitasking is BIG PUSH work through system piles-up work => waste on changes Sequential work PULL work through system Reduces lead time 3

4 More on Team Psychology... Values and development square Friedemann Schulz von Thun Four-sides model Friedemann Schulz von Thun Drama triangle Steven Karpman 4

5 Projects Project components A goal. Typically not well defined A deadline. Often arbitrarily close Some resources. Manpower, money, equipment,... Complexity. Management needed Management Requirements Tasks Schedule Risks Resources 5

6 Planning Phases Draft Initial sketch Go/NoGo decision Refinement/Analysis Collect information, brain-storming Definition of requirements + tasks Implementation (of the plan) Schedule, man-power, budget Execution Perform tasks Team? Responsibility? Power? Controlling Iterations 6

7 Planning Process Similar to SW development process, e.g. waterfall methodology (Bell, Thayer) 1)Capture requirements 2)Design Analysis wikipedia Implementation Execution 3)Implement Often different teams at different phases 4)Evaluate Iterative! 7

8 Simple Projects Single-person, no-budget Still with goal, deadline, complexity and risk E.g. your master-thesis Overall goal + deadline: obvious Analysis Documentation + data management SW Mindmaps, Wikis, etc Information: topics, literature, skills, external dependencies,... Requirements: functionality, performance, language,... Risks: incorrect assumptions, doesn't work, too slow, too late,... Plan-B (several?) Define tasks, dependencies + milestones Plan Project planning SW Do your work! Reserve time for controlling/monitoring 8

9 Larger Projects Human + financial resources Same structure as before plus Resource management Teamwork Team (see last session) Consider even on Skills: hard (task relevant) + soft (team relevant) short-term student groups Personal issues (team/self-oriented, character,...) Cultures (result vs relationship / change vs. stability) Phases: orientation, conflicts, organization, performance Structure Hierarchical: responsibility with leader ( traditional) Flat: responsibility with team ( agile) Even larger projects => ERP (enterprise resource planning) E.g. openerp.com (now Odoo) 9

10 Team Hints Keep in mind: even small (>1), short-term groups are teams Without explicit team-structure members will underperform due to competition for leadership, unclear responsibilities/tasks or personal habit Results will be sub-optimal and/or late Maybe doesn't matter so much Work will be less fun But this one does Even with explicit structure the above might happen Without leader, members should agree on goals, responsibilities and milestones As early as possible Every member can request this to be done 10

11 Software Tools Information Collection Textfiles, databases OneNote (MS) Wikis: ZimWiki Visualisation Drawings, diagrams Maps Cmap Plan MindManager (more powerful) MS-Project Projectlibre Agile (Kanboard) 11

12 Information Collection 12

13 Information Handling Software Wiki: The simplest online database that could possibly work. ( Wikis are frequently used to collect information on WWW servers Users can change content and structure of the data Data: text + document attachements (images, multimedia, doc files, etc) + formatting Structure: All content is held in pages. Page crossreferences can be changes Zim Wiki is a desktop based Wiki Multiple books Wiki-like GUI 13

14 Starting Start ZIM from menu or type zim on the command line Create or select a notebook Select default book 14

15 Configuration Select plugins (edit=>settings=>plugins) Alphabetic sort Task list Attachment browser Screenshot (if avail.) Calendar Tags Calculator Text Search / Topics Backlinks: :target Search / Structure Edit first page 15

16 Get Started Video => Extra Material 16

17 Pages Create a couple of pages and sub-pages Pages can be moved Or renamed Or linked to drop to text area Markdown subset Links ( * Lists 17

18 Add content Apart from formatted text, we can add documents links... and images We can also add files via the attachement folder or via the tools menue Clicking links starts the application (e.g. openoffice) 18

19 Search Search for plain text, tags or for backlinks (to current page) Adding a backlink to a page (e.g. :top:sub) creates that page Pages searchable via desktop tool too (e.g. recoll) 19

20 To Do's Pages can contain to-do items, with due dates and priorities [] ToDo [d: ]!!! All items are listed in the to-do view (need index rebuild) Not aware of interface to external calendar tools 20

21 CMAPs Demo... 21

22 Step 1 Start CmapTools Login with some pwd 22

23 Step

24 Step 2 Select root folder in user area 24

25 Step 3 Default new map is created automatically Create new folder, save map into 25

26 Step 4 Drag sources into new folder from file browser Switch between tree/symbol view NB: German word for Löschen is Keine Treffer 26

27 Step 4 -Video => Extra Material 27

28 Step 5 Create map with concepts (boxes) and propositions (arrows) Drag sources from repository view Use colors, infos, comments, containers, links Layout options: manual, auto layout Create sub-maps 28

29 Step 6 Export CMAP to HTML Flat folder structure with all files, except comments Example: copy tools folder from resources into My_Cmaps Might need to fix links in all cmaps 29

30 Project Planning Software 30

31 Planning Software (Traditional) Basic functionality Definition of tasks and milestones RBS resource breakdown structure Scheduling and dependencies Monitoring Graphical Text/table based Real projects are dynamic WBS work breakdown structure Allocation of resources Progress monitoring Schedule updates Options: alerts, interfaces 31

32 Projectlibre Serves basic functionality plus dynamic updates Limited compatibility to MS Project 32

33 Create Project 33

34 Add Tasks Gantt view Add task names Edit tasks via Infomation tab 34

35 Add Resources 35

36 Assign Resources

37 Assign Dependencies Set appropriate task durations Depends on... Enter task number of predecessor(s) GUI: click on 1st task, pull to 2nd task Task start/end moved, dependency arrow Dependency options End-Start (EA) End-End (EE) Start-End (AE) Start-Start (AA) 37

38 Save Baseline Baseline saves target schedule Indicated by gray lines 38

39 Changes... Tasks Effort Resource Example: day off Change availability of resource Update planning New Gantt schedule indicates slip wrt baseline 39

40 Milestones 40

41 Resource Utilization 41

42 Other Views Pert diagram (Netzplan) Structure, top-down levels, no timing RBS Project evolution and review technique Dependencies, critical path WBS (PSP) Resources 42

43 Large Projects 6 months 300 tasks 10 FTEs 43

44 Modern Project Management Traditional Project Management HEAVY! start: requirements, dependencies, etc Focus on plan and process Inflexible A good idea at a late time is not a gift, it s a threat Agile Manifesto (agilemanifesto.org) 44

45 Agile Workflow Principles Improve/optimize process(es) Small work packages Welcome changes (yes!) Visualize tasks and progress Responsible (cross-functional) teams Kanban (not specific to any flow) Tools/Methods Scrum (Focus: SW development) Observe + measure process, limit WIP Maximize flow, minimize cycle time Maximize velocity Defined roles, self organized teams Iterations (sprints, increments, reviews) Inspect and adapt 45

46 Visualize: Task Boards Scrum Pending FLOW In Progress Kanban Finished Pending AA FLOW In Progress 2 Limited work Finished AA BB BB C C C C D D D D Limited time A, B, C, D: concrete work items (e.g. derived from user stories ) 46

47 Kanban Comic 47

48 Example (cont) 48

49 Example (cont) 49

50 Effort Tracking New task estimates Priority (P) Complexity (C) Duration (D) Sort tasks by weight (W) E.g. W = P/C D Or: value/duration Process top (high weight) to bottom P E Record actual effort Discipline! Daily stand-ups 50

51 Metrics Kanban Cummulative flow Cummulative Flow Diagram Remaining work estimate 35 Initial Actual Ta s k s W o rk [h ] Scrum Burndown chart Pending In Progress Finished WIP 15 Lead time Team s estimate precision will improve over time WIP limited to 4 51

52 Applications Many commercial workflow management applications JIRA, Trello, Projectplace, Zoho, Few free options Self hosted Java/webapps kanboard.net (primarily kanban) kados.info (scrum+kanban) orangescrum.com scrinch (sourceforge.net/projects/scrinch/) Trials/mini: zoho.com, (all free trials) 52

53 Signup to Kanboard Or sign-up 53

54 Edit Profile 54

55 Create (private) Project 55

56 Project Settings Create/rename columns, edit task limits etc 56

57 Limit WIP 57

58 Modified Columns... 58

59 Task Board (1) Add new task 59

60 Add a Task 60

61 Add a Subtask 61

62 Task with some Subtasks 62

63 Subtask View and Timer Subtasks listed in task board 63

64 Convert Subtask to Task => Task Board (2) 64

65 Did some Work => TaskBoard (3) Limit WIP: We cannot have more than 2 items in this column. 65

66 Taskboard Extras Swimlanes Label tasks Cover images Group tasks Categories Illustrate tasks View can be filtered by User, category, status... 66

67 Task Overview 67

68 Project Overview 68

69 Analytics 69

70 Activity Stream 70

71 Gitlab Integration Creating issue on gitlab (gitswarm) creates task on kanboard. Process task until done Close issue on gitlab Task gets removed from kanboard Task history remains in activity stream Gitlab has Kanboard included Limited to issues. Try... 71

72 Gitlab Token Webhook: controller=webhookcontroller&action=handler&plugin=gitlabwebhook&token=2ab2 e d485bf729c5a1f206178f6cd31a9b1c69b1733d6f925eaa3&project_id=5 72

73 Gitlab: GitSwarm de 73

74 Create Gitlab Project 74

75 Setup Kanboard Webhook 75

76 Useful Links Kanban and Scrum Book (free): Free (temporarily) services: J. Preußig, Agiles Projektmanagement, Haufe Verlag Kanban book (free): (unlimited users, single project free) Ziti Kanboard: Sign-up with student 76

77 Project Planning Exercises 77

78 Step 1 Groups of 3 Select (invent) project Preferably different background E.g. Arduino Robot Control Set-up team Leader? Skills? Outline goals, responsibilities Orientation (start) Initial sketch (the HOW) / CMAP Initial requirements, functionalities Remember: Conflict Organisation Performance Strategy things to do, who does what Consider risks (can be virtual) 78

79 Step 2 Initial plan: projectlibre/kanboard Resources (team members, different skills) Initial task set (for the project) Task set (for the exercise) Milestones (for exercise and project) Save baseline Task Columns Subtasks Time estimates PL KB 79

80 Step 3 Use ZIM to collect project relevant resources Plain text, images, screen shots URLs Bibliographic information Arrange information Tags Links Search for something (arduinos, robots, motors, kits,...) Define requirements/user-stories and checklist Can be abstract/non-sense, but from various areas Use cases, non-functional, functional Milestones, dates 80

81 Step 4 PL: Update plan Refine project tasks Dependencies Unexpected delays WBS + RBS Check progress (delays), resource utilization, deadlines Print Gantt and reports Kanboard: Track effort Flow diagram Lead + cycle time 81

82 Step 5 Use CMAPs to visualize important project aspects For exampe: requirements, specification, implementation (or whatever is important) Use different maps with cross-links Use different sources (URLs, images, PDF) Export one particular map to WWW for public distribution Auto layout vs. manual layout Make sure all links are valid 82

83 Step 6 Documentation Use impress (powerpoint) or cmap Project, goals, team structure Tool usage: cmap, zim and planner/kanboard Screen-shots Cmap WWW export (.tgz) Plan: Gannt, Pert/WBS, Milestones Including monitoring Kanboard tasks Summary of SW-tool experience 83

84 Operational Structure Check SW is working: 10' Start with step 1 Team composition (5 persons): 5' Manager (timekeeper, requirements, checklist) Expert 1 (HW: boards, robots) Expert 2 (SW: OS, tools) Initial sketch/cmap: 10' Initial plan/projectlibre or Kanboard: 10' Research/ZIM: 20' Individual areas (req/checklist, HW, SW) Update plan: 10' Visualize/CMAP: 10' Summarize, export + document/impress: 5' ~ 7-10 slides, only screenshots 2 presentations (one pr-libre, one kanban): 2 * 5' Sign in to attendance list 90' 84

85 SW Setup Example software Cmap: Zim: Might need to set private TMPDIR mkdir /tmp/$username export TMPDIR=/tmp/$USERNAME Projectlibre: All tools available in CIP pool except Kanboard (see before) CmapTools, projectlibre, zim Resources asc.ziti.uni-heidelberg.de/sites/default/files/up/pub/wt17/projectplanningall.pdf asc.ziti.uni-heidelberg.de/sites/default/files/up/pub/wt17/tools_resources.tar.gz Cmap: add via add sources => select folder tools. Select all 85

86 Happy Planning... 86