@fwilhe I was tech lead. We had a lot of excellent devs and no PO ... I said yes in a weak moment. I learned a lot since then... from books/blogs/social, from great colleagues , from failures, even from successes. I also had a PSPO training - not too helpful. I also learned to love what I do!
Holzer
- 5 Followers
- 24 Following
- 11 Posts
I do something with software and with people - or is it the other way round?
@BetaCodex
I consider myself being #agile. I think about theories a lot, I even think about thinking about theories. I don't see #agile failing - we are quite successful with it - and apparently it has not "become #scrum".
Btw.: And what is this agile movement thing? Can I join it? Do they have rituals, sth like a secret greeting etc.?
@AgileBob
It depends on how you interprete the phrase:
- Way to go: Doing it (i.e. projects etc.) your own way meets one of the #agile principles, because the team knows what's best for it.
- Anti-pattern: "Being #agile our own way" really is often used simply to cover up lack of courage / justify BS.
It depends on how you interprete the phrase:
- Way to go: Doing it (i.e. projects etc.) your own way meets one of the #agile principles, because the team knows what's best for it.
- Anti-pattern: "Being #agile our own way" really is often used simply to cover up lack of courage / justify BS.
@jchyip #Waterfall is #agile:
Royce's process definition - later called Waterfall - added revolutionary components to a previously inflexible process, including iterations, early testing and UX. AND THAT WAS IN 1970. Can you imagine how expensive it was to develop, deploy and test back then?
He was a pioneer of agile!
Royce's process definition - later called Waterfall - added revolutionary components to a previously inflexible process, including iterations, early testing and UX. AND THAT WAS IN 1970. Can you imagine how expensive it was to develop, deploy and test back then?
He was a pioneer of agile!
@c0c0bird Gilt gefühlt für 80% aller Scrum Master.
@FalkAppel @malcolm because he said POs (i.e. me) are kind of overhead and making the team uneffecient. I cannot survived without an efficient team, so I m doing everything possible to support them (or better: us) .
And of course: Pls never take me 100% serious - I just wanted to get into discussion :-).
And of course: Pls never take me 100% serious - I just wanted to get into discussion :-).
@malcolm @FalkAppel You offend me! Where is stated that a PO must not have programming/Design skills? In my opinion, for quite some products the opposite is true.
@malcolm I think your question is not specific to #agile :-). History tells us that both individual as well as shared power may lead to wrong decicions.
To me, it's all about openess and trust: I am a PO - I decide! I have the feeling the team trusts me. At least, I trust in my team: They WILL force me into strict reasoning/discussions if they don't agree. I explain + listen carefully and learn a lot.
@knechtomat So - mit jetzt durch mit den Statements der erfahrenen Praktiker. Stimme manchmal nur zu 98% überein :-).
Das Schlangenöl-Bild nehm ich mit zum Kunden, das passt super.
Das Schlangenöl-Bild nehm ich mit zum Kunden, das passt super.
@knechtomat
Wenn man als erfahrener Praktiker erst genau hinsehen muss, um herauszufinden, dass #SAFe nicht so wirklich supi ist, hat man glaube ich ein Wahrnehmungsproblem.
Wenn man als erfahrener Praktiker erst genau hinsehen muss, um herauszufinden, dass #SAFe nicht so wirklich supi ist, hat man glaube ich ein Wahrnehmungsproblem.