International conference DevOpsPro in Moscow had been exciting!
1 day of master classes and 2 days of experience sharing, presentations in team building, mindset, kubernetes, docker features, market launch, and many others.
This book is not about Azure or other technical items.
DevOps is about culture, team job, motivation. The book is very detailed and explains DevOps job in details.
I recommend to download and share with your teammates and managers.
Especially recommended for startup teams!
The DevOps Agile skills association renewed the certification roadmap, and the 3rd tier (Leadership level) certifications are available now. I have passed the Product Owner certification one of the first, and want to share a brief experience about this prestigious certification.
The Product Owner role is a leading role to ensure the Product vision, roadmap and backlog, and finally the product value to a customer.
The DASA association actively drives training and certification activities in this area.
The PO certification exam includes 40 questions (in fact, not very complicated, especially if a candidate is good with Scrum and Agile). Each question is followed by 4 answer options, one of those is correct. 26 correct answers (65%) lead to success.
I passed the exam at the first attempt. It seems to me that the certification marks that junior PO is ready for his/her journey.
As any other certification it helps to structure candidate’s skills and practical experience.
3 practical assignments are added to the course “ITIL and DevOps”.
Start-up teams, which deliver and support their products can learn how to implement the ITIL based IT service lifecycle by a single DevOps team.
Now each student can make his/her own exercises according to his/her IT organization specific features and discuss the case with the trainer at the course forum.
Join the training with a lifelong access for $9.99 only.
The first module of the Software requirements training .
Register full training with a first look coupon 65% discount for $11 only!
The training leas You for a full journey from identifying stakeholders, collecting their requirements, expectations, and constraints to balancing requiremebts in a business vs technical requirements matrix; creating prototypes, UML models, and, finally, the SRS document – Software requirements specification.
Improve your skills