143 reputation
6
bio website
location
age
visits member for 2 years, 7 months
seen Sep 19 at 15:02

Jul
11
comment C++ Library API Design
+1: I am finishing reading this book and it is a great resource. Highly recommended.
Jan
9
awarded  Citizen Patrol
Oct
2
awarded  Commentator
Mar
12
comment Scrum for specialists teams
Yes, indeed. So a 15' standup + 15' optional technical meeting could make it maybe. Thanks!
Mar
12
awarded  Scholar
Mar
12
accepted Scrum for specialists teams
Mar
10
comment Scrum for specialists teams
I perfectly agree that communication should still occur. However, sprint planning meetings are just about evaluating story points. If one single person per story can estimate its values, then this meeting is useless... And I believe that the mechanics in Scrum (not agile in general) ARE indeed important.
Mar
10
comment Scrum for specialists teams
Great help! I will check Lean and Kanban! How do we +2 on SE?..;)
Mar
10
comment Scrum for specialists teams
"So I guess they will have to communicate much more as in a team of generalist": this is exactly my point actually. That's why I believe that daily scrum meetings are not enough and should be replaced by weekly meetings. Or daily scrum meetings lasting 30 minutes instead.
Mar
10
awarded  Supporter
Mar
10
awarded  Editor
Mar
10
revised Scrum for specialists teams
Changed wrong usage of "cross-functional" to "generalists" + typos
Mar
9
awarded  Student
Mar
9
comment Scrum for specialists teams
Please flag it as "not belonging here" so that it gets moderator attention. thanks for your help!
Mar
9
comment Scrum for specialists teams
Ok, thanks. Can you migrate this question to programmers.se or must I delete this one and restart a new one there?
Mar
9
comment Scrum for specialists teams
Well, SO has a scrum tag, so I thought I could ask a scrum related question^^. Also, all references I have use a daily scrum of 15 minutes, not 5.
Mar
9
asked Scrum for specialists teams