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

vault backup: 2025-01-15 14:20:05

Browse Source
This commit is contained in:
Claudio Fritsche
2025-01-15 14:20:06 +01:00
parent ca059d0771
commit d0095203ad
6 changed files with 51 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
5 Media/0 Books/More Effective Agile by Steve McConnell.md
View File

@@ -168,6 +168,17 @@ Summarizing: 80% of the work should go into development and 20% into planning an
| 7 | Used consistently and effectively |
| 10 | Optimizing |
### More effective Agile Team Structure
The focus is to have a *cross-functional* team with diverse expertise in different software domains such as front-end, back-end, architecture design, UX design, etc. A typical agile team requires at least the following specializations:
- Developers from different layers of the application (front end, back end, etc) and with different expertise (architecture, user experience, security, etc)
- Testers from different layers of the application
- technical writers
- experts in the development process being used (Scrum Master)
- Subject Matter Experts (e.g. Industry experts)
- Business experts who bring business understanding and ROI to the team (Product Owner)
It is difficult to find a full set of skills and remain small (5-9 people), which is why some people might play multiple roles and the organization should help the members to build those skills.
Beyond skills **Ability and Authority** to make decisions should lie within the team in order for it to implement actual agile
### Enjoy the Fruits of Your Labor
The agile mindset is about decriminalising mistakes and develop a Growth Mindset. Use mistakes as learning opportunities, Inspect and Adapt, and gradually become better.