Difference between revisions of "Beyond XP"
(Created page with ""Post-XP something" (will be replaced by the real name) Attendees - Jesse, Jeffrey, Nat, Yuliya Discussion - Discussed how Cloud Foundry practices changed since VMware acqui...") |
|||
| Line 1: | Line 1: | ||
"Post-XP something" (will be replaced by the real name) | "Post-XP something" (will be replaced by the real name) | ||
| − | Attendees | + | '''Attendees''' |
- Jesse, Jeffrey, Nat, Yuliya | - Jesse, Jeffrey, Nat, Yuliya | ||
| − | Discussion | + | '''Discussion''' |
| − | + | ||
| + | Discussed how Cloud Foundry practices changed since VMware acquisition and pandemic | ||
| + | |||
1. Moved product managers and designers away | 1. Moved product managers and designers away | ||
2. Changed what managers did (80% sw development -> full time manager) | 2. Changed what managers did (80% sw development -> full time manager) | ||
Revision as of 11:22, 4 February 2023
"Post-XP something" (will be replaced by the real name)
Attendees - Jesse, Jeffrey, Nat, Yuliya
Discussion
Discussed how Cloud Foundry practices changed since VMware acquisition and pandemic
1. Moved product managers and designers away 2. Changed what managers did (80% sw development -> full time manager) 3. Not using any co-location enabled practices (eg. breakfast, synchronization)
Alternative approach 1. Empower engineers to groom and own the backlog
Different teams have different problems: sometimes when the question is "who's gonna groom the backlog" people answer "not me", and sometimes there's 2 engineers and 5 people who are trying to tell them what to do, and solutions will be different
Pivotal PMs operating on tactical levels were operating more as business analysts, and couldn't focus on product vision and strategic work.
