With reference to my DevOps Practices group questions/queries, I would like to publish some of the questions in this blog also.
The DevOps experienced readers are invited to comment on the queries/questions below this blog itself for future readers purpose.
I would like to pose the below questions for practitioners.
As we all are aware most of the current DevOps engineers are from the background of Sysadmin roles.
1. When they transition into these modern roles, what kind of issues they might face ?
2. Are they comfortable to mix with Dev and Ops culture ?
3. Can they adopt the Sprint cycles ?
4. As A practitioner what kind of support you might need to give it to them ?
Please let us start our discussion with your opinions through this blog.
=== Please note the following on the agenda of the Facebook group ====>
These questions are created through a DevOps practices group for the professionals who are in DevOps Practices. Their typical roles are; DevOps Engineers, DevOps Architects, DevOps Practioners, etc. Basically the relevant Infra architects also will come into this group like; Cloud architects. But most of our discussions are related to processes, procedures, standards and Implementations.
Please note we are not going to discuss on any tools or cloud services behavior and their usage. There are numerous sites on these areas. You are most welcome to post the issues you face related to improvement of the delivery/sprint cycles through your retrospectives. These can create some actions and outcomes. And all of these can be mapped to the tools those are being used in the projects. This way the new practitioners can learn faster to push the feedback/CDI cycles in their regular projects. Hence the joiners in this group please note all the above and scope of the discussion to scale up yourself. Good luck!
Note: For DevOps technical blogs please visit my site: https://vskumar.blog/
If you are a learner in DevOps, please send a FB request to me. The declined professionals for this group, need to validate as per this description.
With reference to this group agenda, for every member monthly few knowledge sharing discussions participation need to be there to sustain their membership. Totally inactive members are not eligible for continuation.