New answers tagged

1

DevOps is a corporate culture more than a specialization, so that is why each company has its own style, no guideline of how to separate it 'carved in stone'. From my experience of large enterprise projects (plus from the point of view of a business analyst) with DevOps taking a part in it: Infrastructure shared between the projects as a shared source is in ...


3

It does make sense to have some differentiation, however, the proposed differentiations don't make much sense to me. First, it seems like you're using "ops" and "DevOps" interchangeably when they aren't. Operations is a type of work. Operations, or ops, means different things to different organizations. I see it as the set of work needed ...


1

I don't think the separation you are describing is a fundamental one. CI setup is something you can expect to do only once per product and while a different team may be needed to help with that it doesn't necessarily have to be differentiated on the backlog. I'm not sure what you mean by Build, Release and Deployment in this context since the point of having ...


0

Short answer: there is not and official guideline. One could argue (and I often do) that the wording of the Scrum Guide is directive here: Scrum Teams are cross-functional, meaning the members have all the skills necessary to create value each Sprint. I would argue that it doesn't say all the skills necessary to hand the product off to the next team. ...


Top 50 recent answers are included