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!
Learn how Lean principles, a diverse workforce, and a good roadmap all help to build better products with greater speed. 
No comment yet.
Sign up to comment
Scoop.it!
Le framing agile amène les équipes à se préoccuper de la qualité des produits ; et cela passe par la mise en place d’une stratégie softwar
Scoop.it!
On November 4th, 2016 some 300+ IT decision makers gathered in the Amsterdam ArenA for a game-changing DevOps Masterclass: Better, Faster, Smarter with DevOps.…
Scoop.it!
Scoop.it!
Read Part 2 of The DevOps Pilgrimage blog to understand how the Purge automates a centralized build for faster changes and deployment automation.
Scoop.it!
Are you interested in a DevOps transformation for your business? Learn how the Garage practices can help!
Scoop.it!
From
github
Public resources for the book "Team Guide to Metrics for Business Decisions" - SkeltonThatcher/bizmetrics-book
Mickael Ruau's insight:
Example SpreadsheetsWe have created some example spreadsheets to demonstrate what we are talking about in the book. Feel free to use them, copy them, edit them as you like - they should help you get started with metrics for your business decisions! You can find them all in this public folder in google drive: example spreadsheets The folder contains the following spreadsheets: Throughput
Forecasting
(note: the examples are a read-only version. In order to use them use the menu "File/Make a copy" to copy them) Example Trello board
Scoop.it!
To reinvent ourselves, to grow, to become better do we need to destroy our former selves? Some people need to burn all the way down to rise from the ashes like a phoenix. How does losing things you value help you recenter and focus on the things that truly matter? In this talk, learn how mindfulness helps to overcome tragedy and bind together your mental, emotional, physical, and spiritual wellbeing. Jesse Stewart is the founder of AM300 Solutions and author of The Phoenix Project (2019). Jesse was medically retired from the Army after being wounded in combat and multiple surgeries at the rank of Major, at 31 years old. Since retiring he helped found The American 300 non-profit providing college scholarships to all children from the men that fell in Task Force 300, was a Professor (Leadership and Marketing) at Grand Canyon University, and started his own for-profit company. Jesse works tirelessly with Veterans providing guided fly-fishing trips with his father (also a retired disabled veteran), mentoring people across all walks of life dealing with trauma, and working with high performing individuals from US Olympic Athletes to everyday people seeking to be their best version of themselves. This talk was given at a TEDx event using the TED conference format but independently organized by a local community. Learn more at https://www.ted.com/tedx
Scoop.it!
Diaporama de ma session "Agilistes : n'oubliez pas la technique !" lors de la conférence Agile France 2013
Scoop.it!
No matter our views on functional programming vs. object-oriented programming vs. whatever else, we all need to be functional engineers.
Scoop.it!
How The Phoenix Project changed the way I look at my job
|
Scoop.it!
Blog posts about “What is DevOps” are a dime a dozen. I find myself repeating my 0.8 cent version of this, and other buzzwords that people knock aroun
Scoop.it!
This Open Leadership Training Series teaches you best practices in “working open” – a way of working where:
Mickael Ruau's insight:
README
Scoop.it!
DEVOPS contribue à repenser l'organisation des DSI et la façon de fabriquer et délivrer les logiciels.
Scoop.it!
Dans un contexte d’entreprise souvent perçu comme rigide, envisager des changements techniques et organisationnels peut sembler impossible. DevOps est un bon c…
Scoop.it!
Automation is at the heart of Agile engineering practices, and it is a key part of Continuous Delivery (CD) and DevOps culture. Together these techniques reinforce each other, delivering massive productivity and business value.
Scoop.it!
The definition of DevOps, offered by Donovan Brown is "The union of people, process, and products to enable continuous delivery of value to our customers." It accentuates the importance of continuous delivery of value. Let's discuss how experimentation is at the heart of modern development practices.
Mickael Ruau's insight:
Hypothesis-driven development is based on a series of experiments to validate or disprove a hypothesis in a complex problem domain where we have unknown-unknowns. We want to find viable ideas or fail fast. Instead of developing a monolithic solution and performing a big-bang release, we iterate through hypotheses, evaluating how features perform and, most importantly, how and if customers use them.
Every experiment must be based on a hypothesis, have a measurable conclusion, and contribute to feature and overall product learning. For each experiment, consider these steps:
Let's have another look at our sample release with eight hypothetical features.
When we deploy each feature, we can observe user behavior and feedback, and prove or disprove the hypothesis that motivated the deployment. As you can see, the experiment fails for features 2 and 6, allowing us to fail-fast and remove them from the solution. We do not want to carry waste that is not delivering value or delighting our users! The experiment for feature 3 is inconclusive, so we adapt the feature, repeat the experiment, and perform A/B testing in Release X.2. Based on observations, we identify the variant feature 3.2 as the winner and re-deploy in release X.3. We only expose the features that passed the experiment and satisfy the users.
Scoop.it!
Run and scale the IBM Garage Method for Cloud practices, including Enterprise Design Thinking, Lean Startup, agile development, DevOps, and cloud practices, to accelerate the application lifecycle of your enterprise.
Scoop.it!
From
www
The ‘new normal’ world creates three sets of immediate challenges for delivery teams:
Scoop.it!
A real life example of a Phoenix Project war story, learning agile and DevOps the hard way and living to tell about it - a cautionary tale.
Scoop.it!
In the modern era, software is commonly delivered as a service: called web apps, or software-as-a-service. The twelve-factor app is a methodology for building software-as-a-service apps that:
Mickael Ruau's insight:
Who should read this document?
Any developer building applications which run as a service. Ops engineers who deploy or manage such applications. The Twelve FactorsI. CodebaseOne codebase tracked in revision control, many deploysII. DependenciesExplicitly declare and isolate dependenciesIII. ConfigStore config in the environmentIV. Backing servicesTreat backing services as attached resourcesV. Build, release, runStrictly separate build and run stagesVI. ProcessesExecute the app as one or more stateless processesVII. Port bindingExport services via port bindingVIII. ConcurrencyScale out via the process modelIX. DisposabilityMaximize robustness with fast startup and graceful shutdownX. Dev/prod parityKeep development, staging, and production as similar as possibleXI. LogsTreat logs as event streamsXII. Admin processesRun admin/management tasks as one-off processes
Scoop.it!
What metrics and KPIs should you use to track your incident management program? Here are some of the most common options and guidance on when to use them.
|
