obsidian/Main
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

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

Browse Source
This commit is contained in:
Claudio Fritsche
2025-01-09 18:14:27 +01:00
parent 8e708d46ad
commit 95370d9e98
3 changed files with 56 additions and 24 deletions
Download Patch File Download Diff File Expand all files Collapse all files

53
5 Media/0 Books/Software Project Survival Guide by Steve McConnell.md
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?
##### 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