From 95370d9e980247b00fe4e33284896999da3c8216 Mon Sep 17 00:00:00 2001 From: Claudio Fritsche Date: Thu, 9 Jan 2025 18:14:27 +0100 Subject: [PATCH] vault backup: 2025-01-09 18:14:27 --- .obsidian/workspace.json | 26 ++++----- .../Meetings/OneSec Cofounder Verhandlung.md | 1 + ...oject Survival Guide by Steve McConnell.md | 53 ++++++++++++++----- 3 files changed, 56 insertions(+), 24 deletions(-) diff --git a/.obsidian/workspace.json b/.obsidian/workspace.json index d97d1ed..f54cda6 100644 --- a/.obsidian/workspace.json +++ b/.obsidian/workspace.json @@ -92,12 +92,12 @@ "state": { "type": "markdown", "state": { - "file": "Temporary/Untitled.md", + "file": "0 Journal/0 Daily/2024-05-04.md", "mode": "source", "source": false }, "icon": "lucide-file", - "title": "Untitled" + "title": "2024-05-04" } } ], @@ -132,7 +132,7 @@ "state": { "type": "search", "state": { - "query": "job title", + "query": "dimitri", "matchingCase": false, "explainSearch": false, "collapseAll": false, @@ -153,7 +153,8 @@ "title": "Bookmarks" } } - ] + ], + "currentTab": 1 } ], "direction": "horizontal", @@ -527,7 +528,8 @@ "title": "OneSec Cofounder Verhandlung" } } - ] + ], + "currentTab": 1 } ], "direction": "vertical", @@ -573,12 +575,15 @@ } ] }, - "active": "87bd9046756151ba", + "active": "73cc7fa99c62cf7a", "lastOpenFiles": [ - "5 Media/0 Books/Software Project Survival Guide by Steve McConnell.md", - "0 Journal/Meetings/Vidit Update - 8.1.24.md", - "0 Journal/Meetings/OneSec Cofounder Verhandlung.md", + "0 Journal/0 Daily/2024-05-04.md", + "0 Journal/0 Daily/2024-09-25.md", + "0 Journal/Meetings/Dimitri - 12.12.24.md", "Temporary/Untitled.md", + "0 Journal/Meetings/OneSec Cofounder Verhandlung.md", + "0 Journal/Meetings/Vidit Update - 8.1.24.md", + "5 Media/0 Books/Software Project Survival Guide by Steve McConnell.md", "Temporary/Un.md", "Temporary/Jira Tutorial.md", "Attachments/Pasted image 20250108160308.png", @@ -609,9 +614,6 @@ "Templates/Book Template.md", "5 Media/0 Books/TestBook by Mr. Blue.md", "5 Media/0 Books/null by null.md", - "Temporary/Untitled 2.md", - "5 Media/0 Books/ by .md", - "Temporary/Untitled 1.md", "Attachments/Gym-Rings-UK.pdf", "99 Work/Jobhunt/Applications", "99 Work/0 OneSec/OneSecNotes/30 Engineering Skills/Robotics/Sensors", diff --git a/0 Journal/Meetings/OneSec Cofounder Verhandlung.md b/0 Journal/Meetings/OneSec Cofounder Verhandlung.md index 576e974..fb81861 100644 --- a/0 Journal/Meetings/OneSec Cofounder Verhandlung.md +++ b/0 Journal/Meetings/OneSec Cofounder Verhandlung.md @@ -41,6 +41,7 @@ status: not_started - Valuation of the stock option contract - mit Anwalt reden und tax ruling aufsetzen - Was wenn ich es versteuern muss --> 30% mehr anteile + - kosten auf firma #### Responsibility & Freedom to act - written down on paper diff --git a/5 Media/0 Books/Software Project Survival Guide by Steve McConnell.md b/5 Media/0 Books/Software Project Survival Guide by Steve McConnell.md index 7386d2d..44d6464 100644 --- a/5 Media/0 Books/Software Project Survival Guide by Steve McConnell.md +++ b/5 Media/0 Books/Software Project Survival Guide by Steve McConnell.md @@ -463,18 +463,42 @@ Team dynamics and team bond play a more important role than individual developer - Will the individuals work well together? ##### Project Team Organization -- Project manager: orchestrate detailed technical work (development, quality assurance, user documentation). Develops software development plan. Is the team's link to upper management. -- Product manager: Business level work: marketing, product packaging, end-user documentation, end-user support. In-house projects: work with groups that use the system to define the software, setup trraining and user support -- Architect: Responsible for conceptual integrity at design and implementation level -- User-interface designer: responsible for conceptual integrity of software visible to end-user. -- End-user liaison: interact with end-user throughout the project. Walk them through the prototype, demonstrate new releases, gather user feedback. -- Developer: detailed design and implementation of software. Responsible for making the software work -- QA/Testers: responsible for Quality Assurance and test activities. Create detailed test plans and perform tests. Find all the ways to break the software. -- Tool smith: Responsible for developing build scripts, maintain versioning system, developing utilities needed by the project. -- Build coordinator: responsible for maintaining and running the daily build and notifying the developers when something breaks the build -- Risk officer: watch for emerging risks and diversion from the development plan -- End-user documentation specialists: generate help files, documentation and instructional materials that end-users will use. +- **Project manager:** orchestrate detailed technical work (development, quality assurance, user documentation). Develops software development plan. Is the team's link to upper management. +- **Product manager:** Business level work: marketing, product packaging, end-user documentation, end-user support. In-house projects: work with groups that use the system to define the software, setup training and user support. +- **Architect:** Responsible for conceptual integrity at design and implementation level. +- **User-interface designer:** responsible for conceptual integrity of software visible to end-user. +- **End-user liaison:** interact with end-user throughout the project. Walk them through the prototype, demonstrate new releases, gather user feedback. +- **Developer:** detailed design and implementation of software. Responsible for making the software work. +- **QA/Testers:** responsible for Quality Assurance and test activities. Create detailed test plans and perform tests. Find all the ways to break the software. +- **Tool smith:** Responsible for developing build scripts, maintain versioning system, developing utilities needed by the project. +- **Build coordinator:** responsible for maintaining and running the daily build and notifying the developers when something breaks the build. +- **Risk officer:** watch for emerging risks and diversion from the development plan. +- **End-user documentation specialists:** generate help files, documentation, and instructional materials that end-users will use. +> [!important] Mixing Roles is Okay except for ... +> ... Quality Assurance and Development + +#### Time Accounting +Tracking where team members spend their time will help with future planning. + + +> [!question] Survival Check - Preliminary Planning +> - 👍🏼 The project has a clear vision. +> - 💣 The vision doesn't provide guidance in deciding what to leave out of the software. +> - 👍🏼 The project team has identified an executive sponsor or committee with final authority over projectwide decisions. +> - 👍🏼 The project plans and progress compared to the plans are readily available to all project team members and upper management. +> - 👍🏼 The project has a risk officer. +> - 💣 The risk officer is the project manager. +> - 👍🏼 The project has a Top 10 Risks List. +> - 💣 The Top 10 Risks List is not kept up to date. +> - 👍🏼 The project team develops risk-management plans for each risk on the Top 10 Risks List. +> - 👍🏼 The project leaders hire well-qualified people (waiting for qualified people, if necessary), rather than just hiring whoever is available first. +> - 👍🏼 Time accounting is begun before requirements development begins. +> - 👍🏼 All of the above considerations are formalized in a Software Development Plan. +> - 💣 The Software Development Plan isn't placed under change control. +> - 💣 The Software Development Plan isn't actually followed by the development team. + +### Requirements Development --- @@ -488,7 +512,12 @@ Team dynamics and team bond play a more important role than individual developer - Top 10 Risk List (keeps being updated) including a risk-management plan for each risk - Software Development Plan - Risk management approach - - Risk officer + - Risk officer and other roles: personnell strategies + - Decision making authority + - project scope + - publicizing of plans and progress + - time accounting + - once finished sign off by project manager, dev team and Q&A team, then place under change control ## Tool list - Anonymous risk-reporting channel