We reach a point of dimishing returns really quickly just talking about situations. I can share experiences and what I think I know, but at the end of the day this isn't about going off and following some author, speaker, or book. It's figuring out what works in your particular situation.
The cool part about Agile is that it's not Scrum, ie, there is no certification authority or magic recipe. It's just a bunch of schmucks sharing what worked or didn't work.
I shy away from answers like "it's all Scrum" or "It's all Kanban" for just that reason -- too facile. In a 15-project program, you usually have several groups going strictly Kanban. Enterprise architecture is one (if you have that) and program release is another. These things don't have to sync up, they just need to be ready. So even my advice about using sprints isn't absolute. Advice in this area is a lot of generalizations. You get what you pay for!
If you have any experience with these larger structures, I'd love to hear about it. I'm always collecting tidbits like that. Thanks for the chat!
I can share experiences and what I think I know, but at the end of the day this isn't about going off and following some author, speaker, or book. It's figuring out what works in your particular situation
Likewise and ditto. As I said I would imagine that it would be very context dependent.
Comments
We reach a point of dimishing returns really quickly just talking about situations. I can share experiences and what I think I know, but at the end of the day this isn't about going off and following some author, speaker, or book. It's figuring out what works in your particular situation.
The cool part about Agile is that it's not Scrum, ie, there is no certification authority or magic recipe. It's just a bunch of schmucks sharing what worked or didn't work.
I shy away from answers like "it's all Scrum" or "It's all Kanban" for just that reason -- too facile. In a 15-project program, you usually have several groups going strictly Kanban. Enterprise architecture is one (if you have that) and program release is another. These things don't have to sync up, they just need to be ready. So even my advice about using sprints isn't absolute. Advice in this area is a lot of generalizations. You get what you pay for!
If you have any experience with these larger structures, I'd love to hear about it. I'm always collecting tidbits like that. Thanks for the chat!
I can share experiences and what I think I know, but at the end of the day this isn't about going off and following some author, speaker, or book. It's figuring out what works in your particular situation
Likewise and ditto. As I said I would imagine that it would be very context dependent.