vault backup: 2025-01-09 18:14:27

This commit is contained in:
2025-01-09 18:14:27 +01:00
parent 8e708d46ad
commit 95370d9e98
3 changed files with 56 additions and 24 deletions

View File

@@ -92,12 +92,12 @@
"state": { "state": {
"type": "markdown", "type": "markdown",
"state": { "state": {
"file": "Temporary/Untitled.md", "file": "0 Journal/0 Daily/2024-05-04.md",
"mode": "source", "mode": "source",
"source": false "source": false
}, },
"icon": "lucide-file", "icon": "lucide-file",
"title": "Untitled" "title": "2024-05-04"
} }
} }
], ],
@@ -132,7 +132,7 @@
"state": { "state": {
"type": "search", "type": "search",
"state": { "state": {
"query": "job title", "query": "dimitri",
"matchingCase": false, "matchingCase": false,
"explainSearch": false, "explainSearch": false,
"collapseAll": false, "collapseAll": false,
@@ -153,7 +153,8 @@
"title": "Bookmarks" "title": "Bookmarks"
} }
} }
] ],
"currentTab": 1
} }
], ],
"direction": "horizontal", "direction": "horizontal",
@@ -527,7 +528,8 @@
"title": "OneSec Cofounder Verhandlung" "title": "OneSec Cofounder Verhandlung"
} }
} }
] ],
"currentTab": 1
} }
], ],
"direction": "vertical", "direction": "vertical",
@@ -573,12 +575,15 @@
} }
] ]
}, },
"active": "87bd9046756151ba", "active": "73cc7fa99c62cf7a",
"lastOpenFiles": [ "lastOpenFiles": [
"5 Media/0 Books/Software Project Survival Guide by Steve McConnell.md", "0 Journal/0 Daily/2024-05-04.md",
"0 Journal/Meetings/Vidit Update - 8.1.24.md", "0 Journal/0 Daily/2024-09-25.md",
"0 Journal/Meetings/OneSec Cofounder Verhandlung.md", "0 Journal/Meetings/Dimitri - 12.12.24.md",
"Temporary/Untitled.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/Un.md",
"Temporary/Jira Tutorial.md", "Temporary/Jira Tutorial.md",
"Attachments/Pasted image 20250108160308.png", "Attachments/Pasted image 20250108160308.png",
@@ -609,9 +614,6 @@
"Templates/Book Template.md", "Templates/Book Template.md",
"5 Media/0 Books/TestBook by Mr. Blue.md", "5 Media/0 Books/TestBook by Mr. Blue.md",
"5 Media/0 Books/null by null.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", "Attachments/Gym-Rings-UK.pdf",
"99 Work/Jobhunt/Applications", "99 Work/Jobhunt/Applications",
"99 Work/0 OneSec/OneSecNotes/30 Engineering Skills/Robotics/Sensors", "99 Work/0 OneSec/OneSecNotes/30 Engineering Skills/Robotics/Sensors",

View File

@@ -41,6 +41,7 @@ status: not_started
- Valuation of the stock option contract - Valuation of the stock option contract
- mit Anwalt reden und tax ruling aufsetzen - mit Anwalt reden und tax ruling aufsetzen
- Was wenn ich es versteuern muss --> 30% mehr anteile - Was wenn ich es versteuern muss --> 30% mehr anteile
- kosten auf firma
#### Responsibility & Freedom to act #### Responsibility & Freedom to act
- written down on paper - written down on paper

View File

@@ -463,18 +463,42 @@ Team dynamics and team bond play a more important role than individual developer
- Will the individuals work well together? - Will the individuals work well together?
##### Project Team Organization ##### 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. - **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 - **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 - **Architect:** Responsible for conceptual integrity at design and implementation level.
- User-interface designer: responsible for conceptual integrity of software visible to end-user. - **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. - **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 - **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. - **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. - **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 - **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 - **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. - **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 - Top 10 Risk List (keeps being updated) including a risk-management plan for each risk
- Software Development Plan - Software Development Plan
- Risk management approach - 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 ## Tool list
- Anonymous risk-reporting channel - Anonymous risk-reporting channel