Get Started for FREE
Sign up with Facebook Sign up with X
I don't have a Facebook or a X account
 Your new post is loading...
Your new post is loading...
Scoop.it!
Here's Part 3 of The DevOps Pilgrimage blog that leads to the Ascent with functional testing of fresh deployment and upgrade. Click here to learn more. 
No comment yet.
Sign up to comment
Scoop.it!
In series of posts at Agile Gnostic, I explained about the four facets to agility. These four facets of Agile are... Values and Principles Culture & Mindset Methods & Practices Tools and Technologies What I observed is that all these four facets are applicable to DevOps as well. This post introspects these facets from DevOps…
Scoop.it!
A water spider is a Lean production personnel role centered around timely and accurate stock replenishment. The water spider team member is much like a mobile Kanban system that refills the production line with the required materials to maintain a steady flow.
Scoop.it!
The Phoenix Project: A Novel About IT, DevOps, and Helping Your Business Win by Gene Kim, Kevin Behr, George Spafford My rating: 4 of 5 stars This book is in a story form following someone who has …
Scoop.it!
From
dzone
Barry Chandler, DevOpsDays London Organizer, reviews how DevOps is measured, as well as the Japanese lean engineering practices it evolved from.
Scoop.it!
From
dzone
Executing a DevOps process is just as important as tracking its progress and effectiveness through the process and customer and employee satisfaction.
Scoop.it!
Agile Alliance maintains a guide on the practice areas of Agile software development. They include: extreme programming, teams, lean, scrum, product management…
Scoop.it!
From
dzone
With new data protection laws coming into play, and consumers more aware than ever before of how their privacy is being compromised, there is now a requirement for companies to adopt a compliant DevOps approach. Download this Refcard to discover the best practices to adopt compliant DevOps.
Scoop.it!
From
github
The Agile Operations methodology. Contribute to jdumars/agileops development by creating an account on GitHub.
Mickael Ruau's insight:
Note: This is the culmination of years of work managing and optimizing the practice of technical operations groups/DevOps at scale. These are proven tactics and techniques that can be applied across any technical value delivery organization of any size to increase efficiency, satisfaction, and enterprise agility. While I had hoped to write a book on this eventually (see the outline for what that would have looked like), I do not have the time to do so, and yet these topics are extremely relevant especially as the cloud native revolution takes hold. This is not a replacement of DevOps, but instead the overarching framework that DevOps is a part of.
Scoop.it!
Product and Sales can collaborate. How? Learn how you can run a report of associations between Jira issues and Salesforce records, as well as aggregation of information from both platforms.
Scoop.it!
If Site Reliability Engineering (SRE) and DevOps make the Dev and Ops team work together, then, what’s the difference between the two? Check out this SRE vs DevOps article to know more.
Scoop.it!
One such technology is - cloud computing. Slowly, new terms were introduced in clouding. However, there are two terms that are used widely in cloud computing – SysOps (System operations) and DevOps (Development operations).
Scoop.it!
DevOps is not a process, company, tool, person or team. It is a philosophy, a movement that is changing the way we work as IT professionals similar to the way lean manufacturing changed the way companies manufactured goods. It is a change in culture that requires everyone involved in the application life cycle to be responsible for the continuous delivery of value to their end users. DevOps is the key to true marketplace agility.
|
Scoop.it!
Here's a blog to help you start your DevOps Pilgrimage with The Abyss, a conflict-driven unsecure system where long testing cycles and missed deadlines lead to performance degradation.
Scoop.it!
The Phoenix Project PDF Summary by Gene Kim, Kevin Behr, and George Spafford explains the basics of DevOps, an innovative IT management system that is created to help coordination and collaboration among business units, products owners, and different IT operations.
Scoop.it!
I was looking for a good summary of The Phoenix Project and was unable to find one that wasn’t simply a list of DevOps methods and principles, so here you go. I also found it hard to follow the character’s roles within the organization, so I have included an org chart as well.
Scoop.it!
From
medium
The phoenix project Gene Kim, Kevin Behr and George Spafford was in my reading list for a quite long time. Finally was able to read and I must say was not able not keep it away until the end. While…
Mickael Ruau's insight:
Apart from the 3 ways, the book talks about the 4 categories of work
Scoop.it!
From
dzone
These messages from top DevOps minds like Gene Kim give advice on continuous delivery, aligning with business objectives, and departments working together.
Scoop.it!
The Agile Landscape v3 is a visualization of many of the methodologies within the Agile Process by Chris Webb from Deloitte that uses the visualization design style of a subway map to group related activites and the show connections.
Mickael Ruau's insight:
Being Agile isn’t as simple as following one single methodology. In fact, Agile encompasses a number of different practices and frameworks, often referred to as “the Agile umbrella.” For an organisation to be successful in adopting Agile ways of working, it requires the right technique/method to be used to address the problem or need. Given there are so many different Agile frameworks, a challenge many organisations or individuals face is deciding which framework to use and in which context. In this post, we use an analogy to help bring some light to this. We like to conceptualise Agile as a highly interconnected landscape of practices transporting ideas across zones to value. There is no perfect starting point, nor an express line or a direct route suiting all conditions.We’ll leave you to explore the Agile Landscape, and leave you with this:
Scoop.it!
Presentation from Enterprise DevoOps Summit in San Francisco - October 2014 Set in the context of an Enterprise Data Warehouse, this session will tell the stor…
Scoop.it!
Kevin Lee, Industry Solutions Consultant, Pilgrim Quality Solutions Can you capture or even approximate the cost of quality defects? Is it possible to put a price on a true or potential product recall? For manufacturers whose products can mean the difference between life and death, the cost
Scoop.it!
Transitioning from sysadmin to DevOps will have a cost in time and effort but will be worth it. Your benefits will include new skills, advanced tools, and fresh perspective.
Scoop.it!
DevOps and SREs have dashboards to monitor services and product performance, and now it's time for us to understand how to measure these teams' performance as well.
Mickael Ruau's insight:
DevOps and SREs have to stay on top of everything that’s happening inside the application. They need to have a real-time monitoring system, that will help them see the application uptime, load time, number and success of API calls, CPU process threads, memory usage and other metrics. And while it is their job to make sure everything is up and running, we want to make sure they’re doing it as expected. To do so, we also need to look across the entire application and workflow to find the answers and data about every parameter we’re interested in. These usually include:
Each one of these parameters contains a world of metrics and calculations, and trying to monitor all of them is like trying to photograph an entire fireworks show on the Fourth of July: you can do it, but you’re missing the point. To help us help ourselves, we need to narrow down what we’re looking at. And since our goal is to measure our own teams and operations, it’s easier to take a step back and have a broader look at everything. Now, let’s turn these analogies into practices.
Scoop.it!
Retour d’expérience – “If you’re not embarrassed by the first version of your product, you’ve launched too late.” (Reid Hoffman, fondateur de LinkedIn). Se lancer sans se sentir encore prêt serait une règle d’or qui vient heurter, bien souvent, notre désir de perfection. Mais aussi notre peur du regard de l’autre, notre crainte de l’erreur… et plus encore notre redoutable phobie de l’échec. Dans ce contexte, la méthode du “Test and Learn” est un moyen de passer à l’action, de lutter contre l’immobilisme. Voici quelques pistes pour lever nos blocages. Par Jérôme Adam, Conférencier-Entrepreneur.
Mickael Ruau's insight:
Sortir de sa zone de confort via un panel critique et constructifÉtape 1 du Test and Learn : “Dans un premier temps les chantiers sont souvent déployés à une échelle réduite (échantillon représentatif…) afin de détecter rapidement les problèmes à rectifier.” Pour tester son projet et ses idées, il faut bien sûr choisir des personnes dans lesquelles on peut placer sa confiance. Mais placer sa confiance n’impose pas de choisir des personnes qui nous ressemblent. Ni d’aller sur des terrains où nous sommes sûrs de réussir, de plaire, de recueillir l’assentiment. Dans le cas de ma conférence, je me suis adressé à des chefs d’entreprise, des entrepreneurs, des managers, artistes, personnes engagées. Un panel d’une vingtaine de personnes, un mix entre celles qui me connaissaient à titre professionnel ou personnel, et celles qui ne m’avaient croisé qu’une ou deux fois. Il m’avait semblé intéressant de voir comment ces personnes accueilleraient des thématiques sur lesquelles je n’étais pas identifié et de sentir comment leur perception serait biaisée ou non en fonction de ce qu’elles connaissaient de moi.
Envisager la critique et l’erreur comme un moyen d’avancerÉtape 2 : “Ensuite interviennent plusieurs phases de correction par mode de Feedback.” Se prêter au jeu des critiques peut être déstabilisant, c’est vrai. L’exercice invite à l’humilité et à ne jamais oublier que les remarques reçues concernent avant tout une idée, un projet. Il faut éviter à tout prix de prendre à titre personnel les retours, les corrections suggérées. Se tromper ou à tout le moins ajuster le tir doit avant tout être perçu comme le moyen d’avancer.
Ajuster tout en faisant preuve de discernementDernière étape : “Une fois les tests concluants le projet pourra être déployé complètement.”
Scoop.it!
The Three Amigos not only transfers siloed thinking into cooperative synergy, the process also assists in clarifying the entire deployment pipeline.
|
