Devops for Growth
121.0K views | +6 today
Devops for Growth
For Product Owners/Product Managers and Scrum Teams: Growth Hacking, Devops, Agile, Lean for IT, Lean Startup, customer centric, software quality...
Curated by Mickael Ruau
Your new post is loading...
Your new post is loading...

Popular Tags

Current selected tag: 'architecture'. Clear
Scooped by Mickael Ruau
June 2, 2019 6:23 AM
Scoop.it!

The Best Programming Languages for Each Situation, Part 1 - DZone Agile

In this post, we examine how you can know which programming language is best for you and your team, and few a use cases of big companies switching languages.
No comment yet.
Scooped by Mickael Ruau
May 28, 2019 3:15 PM
Scoop.it!

Agile Architecture Method –

Agile Architecture Method – | Devops for Growth | Scoop.it
I presented our new patterns & practices Agile Architecture Method for the first time at the patterns & practices Summit.   Our Agile Architecture Method is an iterative and incremental approach for designing architectures.  To summarize, it’s a technique that: Scopes and focuses your architecture exercise. Uses scenarios to drive the design and evaluate potentia
Mickael Ruau's insight:

Iterative and Incremental Design 
You can iteratively flesh out your architecture as you work through your design and discover more details that impact your architecture.  You don’t have to design your architecture in a single iteration. Do not get lost in the details; focus on the big steps and build a framework on which you can base your architecture and design.

My Related Posts

 

 

No comment yet.
Scooped by Mickael Ruau
May 20, 2019 6:22 AM
Scoop.it!

The Best Programming Languages for Each Situation, Part 2 - DZone Agile

In Part 2 of our series, we explore languages such as Python, C++, and Erlang, and their impact on developers in industry, academia, and game development.
No comment yet.
Scooped by Mickael Ruau
May 1, 2019 6:18 PM
Scoop.it!

The Power of Blue Books for Platform Impact –

Why invest in prescriptive guidance or “Blue Books” for Microsoft platform impact?  While the answer is obvious to many, it’s not as obvious to others, so I’ll attempt to paint the picture here. 

Mickael Ruau's insight:
Here is a summary of the impact that can help you better understand the value of Blue Books from a broader perspective.

 

Blue Book Results Application Architecture Guide, Second Edition
  • The platform playbook for Microsoft’s application platform
  • Canonical application types for Web app, RIA, Rich Client, Mobile, and Web Services
  • Baseline best practices for application architecture and design
  • Templates baked into Visual Studio
  • Praise from Ray Ozzie
  • Praise from Grady Booch
  • Conceptual Framework for Application Architecture
Building Secure ASP.NET Applications
(aka The first official Microsoft “Blue Book”)
  • End-to-End Application Scenarios for Web Apps
  • Created a highly reusable set of Application Patterns
  • Baseline architectures and success patterns shared broadly inside and outside Microsoft
Improving .NET Application Performance and Scalability
(aka “Perf and Scale”)
  • Repeatable performance model
  • Created a highly-effective method for performance modeling
  • Performance Engineering approach baked into Visual Studio
  • 4 patents filed for performance engineering
  • Performance Engineering approach widely adopted inside and outside Microsoft
  • Used for offerings in Microsoft Consulting Services
  • Rules baked into Microsoft Best Practices Analyzer Wizard (MBPA)
Improving Web Application Security 
(aka “Threats and Countermeasures”)
  • Repeatable security model for Web applications
  • Created a highly-effective method for threat modeling
  • Created a knowledge base of threats, attacks, vulnerabilities, and countermeasures
  • Security model for network, host, and application security
  • Security Engineering approach baked into Visual Studio
  • 4 patents filed for application security
  • Used for offering in Microsoft Consulting Services
  • Rules baked into Microsoft Best Practices Analyzer Wizard (MBPA)
Improving Web Services Security
  • Security model for Web Services
  • End-to-End Application Scenarios for Web Services
  • Created a highly reusable set of Application Patterns
  • Baseline architectures and common success patterns shared broadly inside and outside Microsoft
Performance Testing Guidance for Web Applications
  • Created a highly-effective method for performance testing Web applications
  • Performance Testing approach widely adopted inside and outside Microsoft
  • Used for offerings in Microsoft Consulting Services
Security Engineering Explained
  • Created a model for baking security into the life cycle
  • Helped shift thinking from security "reviews" to "inspections"
  • Overlays security-specific activities on product development life cycles
No comment yet.
Scooped by Mickael Ruau
March 22, 2019 4:56 AM
Scoop.it!

Encore un article sur le packaging par features

Encore un article sur le packaging par features | Devops for Growth | Scoop.it


Il n’est question que de la manière de ranger des fichiers dans des dossiers, quels impacts cela peut-il avoir ? Aussi étrange que cela puisse paraître cela va impacter :

La cohésion globale de l’application ;
La capacité à maîtriser les API internes de l’application ;
La facilité d’accueil de nouveaux développeurs ;
La capacité de l’application à accueillir sereinement les nouvelles features ;
Un éventuel découpage en plusieurs applications distinctes.

C’est en tout cas ce que je vais essayer de montrer dans les paragraphes suivants. Cependant, il ne faut pas me croire. Je vous invite à faire vos propres essais et à choisir la méthode qui vous convient le mieux.
No comment yet.
Scooped by Mickael Ruau
March 4, 2019 7:56 AM
Scoop.it!

Mon avis sur le livre Clean Architecture par Robert C. Martin

Mon avis sur le livre Clean Architecture par Robert C. Martin | Devops for Growth | Scoop.it
Je vais vous parler du dernier livre écrit par Robert C. Martin (alias Uncle Bob) intitulé *Clean Architecture: A Craftsman's Guide to Software Structure and Design*.
Mickael Ruau's insight:

Le livre explique comment appliquer des principes et techniques qui amènent vers des applications maintenables dans le temps.

Voici la liste des sujets couverts dans ce livre :

  • Introduction : définition de design et architecture.
  • Paradigmes de programmation (structurée, orientée objet, fonctionnelle).
  • Principes SOLID en programmation orientée objet (Responsabilité unique, Ouvert/fermé, Substitution de Liskov, Ségrégation des interfaces, Inversion des dépendances).
  • Principes SOLID appliqués aux composants.
  • Bonnes pratiques de structuration et de déploiement d’application.
  • Comment délimiter les composants ?
  • Pourquoi les bases de données, les frameworks et les interfaces utilisateur ne sont que des détails dans une bonne architecture ?

L’introduction nous rappelle que l’architecture d’un logiciel n’est pas le problème le plus urgent bien qu’elle soit importante pour l'évolution de l'application dans le temps. En contraste, l’intégration de nouvelles fonctionnalités est toujours urgente pour produire de la valeur. Le rôle de l’architecte est donc de conserver l’équilibre.

No comment yet.
Scooped by Mickael Ruau
February 28, 2019 2:27 PM
Scoop.it!

Perpetual evolution--the management approach required for digital transformation | McKinsey

Perpetual evolution--the management approach required for digital transformation | McKinsey | Devops for Growth | Scoop.it
Companies that commit to continually updating their enterprise architectures can deliver goods and services as fast as Internet-born competitors do.
Mickael Ruau's insight:

To stay competitive in a world in which providing a great customer experience has become paramount, companies in nearly every industry must continually innovate digital products and services, as well as the business processes that support those products and services. They can gain greater agility if they abandon rigid enterprise-architecture-management practices of the past and adopt a new approach that enables perpetual evolution—changing out elements of enterprise architecture quickly, adding new parts in no time, and incorporating the latest and greatest functionality. This shift in methodology can help traditional companies keep pace with digital-born competitors.

No comment yet.
Scooped by Mickael Ruau
January 30, 2019 10:51 AM
Scoop.it!

Technos et Stacks des entreprises | Welcome to the Jungle

Technos et Stacks des entreprises | Welcome to the Jungle | Devops for Growth | Scoop.it
Trouvez les entreprises qui vous correspondent en fonction des technologies qu'elles utilisent côté backend (Ruby, PHP, Python, etc.) ou frontend (React, Angular, etc.) mais aussi en fonction de ce qu'elles utilisent côté monitoring, intégration continue, etc.
Mickael Ruau's insight:

861 stacks à découvrir

No comment yet.
Scooped by Mickael Ruau
January 28, 2019 4:15 AM
Scoop.it!

Code Complete: Design in Construction | Microsoft Press Store

Code Complete: Design in Construction | Microsoft Press Store | Devops for Growth | Scoop.it
Small projects benefit from careful design just as larger projects do, and recognizing design as an explicit activity maximizes the benefit you will receive from it.

cc2e.com/0578

Contents

Design Challenges

Key Design Concepts

Design Building Blocks: Heuristics

Design Practices

Comments on Popular Methodologies

Related Topics

Software architecture: Architecture Prerequisite

Working classes: Chapter 6

Characteristics of high-quality routines: Chapter 7

Defensive programming: Chapter 8

Refactoring: Chapter 24

How program size affects construction: Chapter 27
No comment yet.
Scooped by Mickael Ruau
January 18, 2019 6:18 AM
Scoop.it!

An Incremental Architecture Approach to Building Systems

An Incremental Architecture Approach to Building Systems | Devops for Growth | Scoop.it
Most applications we have globally, maybe 90% of them, are perfectly served by a monolithic approach. To avoid overengineering, we should start with a simple architecture and evolve it as needs arise, Randy Shoup recently declared in a presentation where he described his experience with companies that started small and then grew into large global internet companies.
No comment yet.
Scooped by Mickael Ruau
January 11, 2019 10:06 AM
Scoop.it!

The Path to Becoming a Software Architect – Nikolay Ashanin –

Have you ever wondered what career opportunities a developer has? What directions are open, beyond what horizons to grow. And most importantly, where are developers beyond the age of 45? Is there a…
No comment yet.
Scooped by Mickael Ruau
December 29, 2018 9:12 AM
Scoop.it!

Mais qui sont ces singes du chaos ? - 15marches

Mais qui sont ces singes du chaos ? - 15marches | Devops for Growth | Scoop.it
Personne n'a envie de voir son entreprise détruite sans pouvoir se défendre. Les startups de la Silicon Valley ont donc inventé un logiciel pour simuler les pires attaques aléatoires : le Chaos Monkey. Plus qu'un outil, un mode de vie.
No comment yet.
Scooped by Mickael Ruau
November 19, 2018 11:34 AM
Scoop.it!

Thinking Architecturally

Thinking Architecturally | Devops for Growth | Scoop.it

 

In this ebook, solution architect Nathaniel Schutta guides tech leads, senior developers, junior developers, and of course, practicing architects through the process of appraising promising new technologies.

Mickael Ruau's insight:
  • Get guidelines, techniques, and advice for evaluating new tools and technologies
  • Determine the unique needs your project before deciding which technology to use
  • Examine documentation, codebase, testability, and other criteria when evaluating new tools
  • Learn approaches for introducing new technology to skeptical people in the company and on your team
  • Manage the quality attributes of your system once new technology is introduced
  • Learn practical techniques to stay current in an ever evolving industry
No comment yet.
Scooped by Mickael Ruau
May 29, 2019 8:26 AM
Scoop.it!

Métier : concepteur de SI antifragile

Pourquoi avoir peur de l’imprévu ? Et si nous apprenions à en tirer parti ? Voici le message d’"Antifragile", un livre de Nassim Taleb. A appliquer, en urgence, à nos systèmes d’information ?
No comment yet.
Scooped by Mickael Ruau
May 23, 2019 3:46 AM
Scoop.it!

Agile for Infrastructure



Implementing Kanban is less obtrusive than other forms of Agile since you can apply the principles directly to your existing process without having to change it. Start by visualizing the work in progress in your current system. Once you visualize work as it moves from state to state within your system, you can determine where bottlenecks occur and apply WIP (work in progress) limits to smooth the flow over time.

Let’s walk through an example of applying Kanban to an infrastructure environment using an approach created by David Anderson from his book Kanban: Successful Evolutionary Change for Your Technology Business.
No comment yet.
Scooped by Mickael Ruau
May 9, 2019 3:56 AM
Scoop.it!

Release Planning: Don’t let dependencies dictate when your team delivers value —

You’re the product owner and things have gone fairly well on your Agile team.  The team has been producing value on a regular cadence; they are actually working TOGETHER and producing more than the sum of the parts.  The team is getting an idea of how much they can get done in a sprint (their velocity).  They are now asking, “When does this end?” or “When are we going to release this stuff?” or “I know we’re going to California together but I’m not sure if we’re getting there through Texas or South Dakota.”  What to do next?  One way to give that light at the end of the tunnel is Release Planning.

 

Hopefully, your Agile Coach has experience with this.  If not, stop and get someone who has done this before.  It is not something one can read from a book and facilitate a team to do – at least, not well.  

No comment yet.
Scooped by Mickael Ruau
April 30, 2019 10:35 AM
Scoop.it!

A two-speed IT architecture for the digital enterprise | McKinsey

A two-speed IT architecture for the digital enterprise | McKinsey | Devops for Growth | Scoop.it
Delivering an enriched customer experience requires a new digital architecture running alongside legacy systems.
No comment yet.
Scooped by Mickael Ruau
March 8, 2019 3:20 AM
Scoop.it!

Agile Architecture

Agile Architecture | Devops for Growth | Scoop.it
Matthew Parker attempts to dispel the myth that architecture does not need to be agile.
No comment yet.
Scooped by Mickael Ruau
March 3, 2019 5:20 AM
Scoop.it!

The Best Programming Languages for Each Situation, Part 3 - DZone Agile

We wrap our series on the best programming languages for a given situation by taking a look at languages such as Swift, JavaScript, Prolog, and Haskell. Enjoy!
No comment yet.
Scooped by Mickael Ruau
February 3, 2019 5:58 AM
Scoop.it!

Concepts orientés-objet avancés appliqués au développement agile

No comment yet.
Scooped by Mickael Ruau
January 28, 2019 4:55 AM
Scoop.it!

Eliminate dependencies, don’t manage them

Eliminate dependencies, don’t manage them | Devops for Growth | Scoop.it
If you worked in large organizations you have probably heard about the term "dependencies". I am convinced that dependencies need to be eliminated, not managed. With a help of system diagrams in this article, I will uncover the main reasons why Scrum Teams suffer from dependencies, how they impact organizational agility, and what the fundamental solutions to this issue are.
No comment yet.
Scooped by Mickael Ruau
January 24, 2019 1:23 AM
Scoop.it!

Advanced Topic – Organizing by Features and Components – Scaled Agile Framework

Advanced Topic – Organizing by Features and Components – Scaled Agile Framework | Devops for Growth | Scoop.it

Features and components embody two key abstractions used to build software and systems: Features are those behaviors of the system that directly fulfill some user need Components are distinguishable system parts that provide and encapsulate common functions needed to implement features Agile’s continuous delivery emphasizes features (and constituent stories) that solve user needs and differentiate solutions. However, resilient large-scale systems are built out of components that provide for separation of concerns, foster re-use, and improve testability.

 

© Scaled Agile, Inc.
Include this copyright notice with the copied content.

Read the FAQs on how to use SAFe content and trademarks here:
https://www.scaledagile.com/about/about-us/permissions-faq/
Explore Training at:
https://www.scaledagile.com/training/calendar/

No comment yet.
Scooped by Mickael Ruau
January 17, 2019 3:54 AM
Scoop.it!

Architectural Decision Records

Architectural Decision Records | Devops for Growth | Scoop.it
adr.github.io : Homepage of the ADR GitHub organization
No comment yet.
Scooped by Mickael Ruau
December 31, 2018 1:55 AM
Scoop.it!

Limitations et extensions des méthodes agiles — Wikipédia

Limitations et extensions des méthodes agiles - Wikipédia

Les méthodes agiles sont des groupes de pratiques pouvant s'appliquer à divers types de projets, mais se limitant plutôt actuellement aux projets de développement en informatique ( conception de logiciel). Les méthodes agiles ne sont pas apparues avec le Manifeste agile en 2001 mais celui-ci détermine leur dénominateur commun (consacre le terme d'" agile " pour les référencer).

Mickael Ruau's insight:

Sommaire

No comment yet.
Scooped by Mickael Ruau
December 3, 2018 4:48 AM
Scoop.it!

Software Architecture - The Difference Between Architecture and Design

Many people don’t really know the difference between software architecture and software design. Even for developers, the line is often blurry and they might mix up elements of software architecture…
No comment yet.