Devops et agilité
70.2K views | +7 today
Follow
 
Devops et agilité
DEVOPS, agilité, tests, déploiement, sécurité
Curated by Mickael Ruau
Your new post is loading...
Your new post is loading...
Scooped by Mickael Ruau
Scoop.it!

Zoohackathon : Coder pour mettre fin au braconnage

Free Spirit Foundation, l’ambassade des Etats-Unis de France et le Ministère des Affaires étrangères américain s'associent pour organiser un Hackathon en ligne à l’échelle européenne, qui s’inscrit dans la lutte contre le trafic illégal d’animaux et le braconnage. Cet événement aura lieu virtuellement du 6 au 8 Novembre 2020.
Mickael Ruaus insight:

Site et plus d'informations : itfortheplanet.org/about-the-hackathon-2020

Pour s'inscrire : itfortheplanet.org/register

No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Ressources de DevOps – Amazon Web Services (AWS)

Ressources de DevOps – Amazon Web Services (AWS) | Devops et agilité | Scoop.it
Guides, didacticiels et livres blancs

Guides et tutoriels

Guide de démarrage AWS pour DevOps
Ce guide contient des informations sur les services AWS pour le DevOps, ainsi qu'une procédure vous permettant d'expérimenter avec ces services.

Tutoriel de 10 minutes : déployer du code sur une machine virtuelle

Tutoriel de 10 minutes : configurer un pipeline de développement continu
Mickael Ruaus insight:

Présentations sur l'intégration et la livraison continues

Démarrez avec la livraison continue sur AWS

YouTube | Slideshare

DevOps at Amazon: A Look at Our Tools and Processes

YouTube | Slideshare

Turbocharge Your Continuous Deployment Pipeline with Containers

YouTube | Slideshare

Continuous Delivery to AWS Lambda

YouTube | Slideshare

AWS CodeDeploy: Automating Your Software Deployments

YouTube | Slideshare

No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Certified Scrum Developer® : Software Craftsmanship | AGILBEE

Certified Scrum Developer® : Software Craftsmanship | AGILBEE | Devops et agilité | Scoop.it
Mickael Ruaus insight:

 

Programme indicatif

 

Jour 1 Partie I. Scrum
  • Introduction à Scrum et aux Pratiques d’ingénierie logicielle Agile
  • Fonctionnement des 5 jours
  • Scrum
    • Transparence, introspection, adaptation et leadership
    • La science de Scrum
    • Atelier : Optimiser sa production
    • Scrum dans la pratique
    • Atelier : ScrumGame
    • Création et gestion du "Product Backlog"
    • Atelier : Le Product Backlog
Jour 2
  • Ecrire les User Stories et leurs tests de recette
    • Atelier : Création d'un projet
    • Atelier : Remanier les User Stories
  • Collaboration
    • Travailler ensemble comme une seule équipe
    • Inclure le client dans le processus
    • Atelier : Réunion quotidienne d'enfer
    • Définition of "Done"
    • Rétrospective
    • Principe du Pair Programming
    • Autre mode de collaboration
Jour 3 Partie II - Pratiques d’Ingénierie Agile Cette partie est réalisée dans un mode en immersion. Tout le contenu est réalisé en travaillant sur ordinateur.
  • Architecture et Conception
    • Principes d'architecture dans un environnement Agile
    • Pratique de Conception dans une équipe Agile
    • Principes qui permet d'amplifier facilement la testabilité et le Refactoring
  • Test Driven Development
    Etude du développement à base de "Test-First" incluant les concepts suivants :
    • Définition et Principes
    • Théorie et xUnit
    • Les 3A
    • Gérer les exceptions
Jour 4
  • Refactoring
    • Conception émergeante
    • Test Driven Design
    • Quand faut-il refactorer ?
    • Comment éviter les grandes dettes techniques
    • Refactoring pour la maintenance
  • Les meilleures practiques de Développement Agile
    • Conditions Limites
    • TDD et Gestion de base de données SGBDR
    • TDD et Gestion des données liées aux fichiers et aux repository (SVN, Git, Sourcesafe)
    • TDD et Gestion des IHM
  • Techniques avancées avec le TDD
    • Corriger des anomalies
    • Gérer la montée en charge et la sécurité des produits NTIC
    • Gestion de la sécurité logicielle
    • Gestion de la performance
    • Stress tests
  • Les objects Mock
    • Mock, Stub et Fake
    • Application de la théorie sans utiliser de bibliothèque
    • Découverte des bibliothèques du marché
Jour 5 : Sujet au choix
  • Self-Test et Outils collaboratifs
    • Intégration Continue (SVN, CVS, Sourcesafe)
    • Intégrateur Continu (Hudson, Cruisecontrol)
    • Couverture
    • Test Driven Requirement avec Fitnesse
    • Behaviour Driven Development
  • Immersion
    • TDD en environnement complexe avec Integration Continue et Test Driven Requirement (Fitnesse)
  • Coding Dojo
    • Behaviour Driven Development par la pratique
    • Gros refactoring par la pratique
    • Test Driven Requirement avec Fitnesse par la pratique
    • Scala et TDD pour les Développeurs Java
    • ASP.Net MVC 2 et TDD par la pratique
    • Spring et TDD par la pratique
    • C++ and TDD for .Net developers par la pratique
  • Agile Dojo
    • Agile Estimating and Planning dans la pratique : Simulation des Projets et Refactoring de UserStories
    • Facilitation et Practique
  • Conclusion
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

10 Coachs agile freelances sélectionnés par

10 Coachs agile freelances sélectionnés par | Devops et agilité | Scoop.it
Vous cherchez un coach agile pour former vos équipes et vous accompagner dans vos projets ? Découvrez une sélection de freelances, puis la liste complète des profils disponibles. Les meilleurs sont sur Malt ! Contactez-les gratuitement.
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

DEVOPS - La synthèse

DEVOPS contribue à repenser l'organisation des DSI et la façon de fabriquer et délivrer les logiciels.
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

StoriesOnBoard Alternatives and Similar Software - AlternativeTo.net

StoriesOnBoard Alternatives and Similar Software - AlternativeTo.net | Devops et agilité | Scoop.it
Popular Alternatives to StoriesOnBoard for Web, Software as a Service (SaaS), Windows, Mac, Linux and more. Explore 7 apps like StoriesOnBoard, all suggested and ranked by the AlternativeTo user community.
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

« Être Craftsman, c’est un état d’esprit » - NOVENCIA Blog

« Être Craftsman, c’est un état d’esprit » - NOVENCIA Blog | Devops et agilité | Scoop.it
Dans la réalité, assez souvent, on nous demande de développer une solution mais pas de résoudre un problème. Ce qui n’est pas viable, sur le moyen terme, puisqu’à aucun moment du développement, on répond de manière intelligente et technique aux besoins utilisateurs.

Être Craftsman c’est donc agir par itération, être capable de comprendre un problème et le résoudre. Mais aussi chercher et trouver des axes d’amélioration sur l’outil. Avec pour objectif final, la satisfaction utilisateur que ce soit pour lui faire gagner du temps ou en nouvelles fonctionnalités.
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

How to Develop a Quick Start Guide That Prevents Calls and Emails

How to Develop a Quick Start Guide That Prevents Calls and Emails | Devops et agilité | Scoop.it
A Quick Start Guide can help cut down on the number of calls and emails from your new customers. Learn how to create this valuable type of documentation.
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Building your First Agile Team Charter

Building your First Agile Team Charter | Devops et agilité | Scoop.it
Unwritten Team Rules Are Not Enough

It’s likely that most teams already have a set of unwritten rules that govern how they function. However, it’s nearly impossible for unwritten rules to effectively act as a team’s “North Star.”

This is because unwritten rules:

have a tendency to get ignored, forgotten, or misconstrued
are understood differently by various team members
are invisible to new members of the team, which makes it difficult for them to onboard easily
cannot be improved upon incrementally

Building team charters emerged as a means to remove miscommunications around the team’s values and the behaviors they deliver.
Mickael Ruaus insight:

The Perfect Agile Team Charter

What does the optimal team charter look like? When we kick off new Agile marketing teams, we emphasize that team charters work best when they are:

  1. Timely:

    The first team charter should be put together as close to the team’s inception as possible.
  2. Succinct:

    This document should contain up to a maximum of 10 team rules that the members can know well. If the team charters ends up becoming a list of 100 rules, many will be neglected. Keep it short, sweet, and top of mind.
  3. Team-created:

    As all team members will be accountable for following the rules of the charter, it should reflect the beliefs of this group of people, not their managers. As new members join the team, the charter can evolve.
  4. Actionable yet abstract:

    Rules in the charter should be phrased in such a way that team members can definitively say whether they are getting done or not. However, they can also reflect abstract practices and feelings, such as pride and offering support.
  5. Dynamic yet dependable:

    This is a living document. Allow the team charter to change based on new information that comes into the team. But, make sure it’s not changing as often as every day or every week; this level of frequency will cause confusion.
  6. Realistic:

    Keep the team rules outlined in the charter reasonable based on what the team can do now, not what the team wishes they might be able to do in ideal circumstances.
  7. Accessible:

    Word documents or PDF files on your computer don’t make good team charter formats. Put a sheet of paper on the wall of the space you share with your team members, if you’re colocated. If not, change everyone’s computer backgrounds to the charter.
  8. Agreed upon:

    It’s essential that the whole team believes in the contents of the charter. During its creation, give everyone on the team ample time and space to contribute; don’t steamroll quiet team members.

 

No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Agile Team Charters- the Basics

Agile Team Charters- the Basics | Devops et agilité | Scoop.it

Mainly because blank pages often make it hard to get started, here is a Google Doc template that you can fork/copy (or download as MS Word if you roll that way): Agile Team Charter Template.

Mickael Ruaus insight:

Quick Notes on Creating an Agile Team Charter

1. Use a Problem Focus

For reasons I described above, this is probably the most important part of the charter. For bonus points, make sure you know what problems your company or division is solving and how your team and your peer teams fit into that (charter-wise).

2. Note Members & Roles

It may seem obvious but this is probably worth taking 5 minutes to do. Depending on what agile methodology you’re using, note the Product Owner, Scrum Master/Coach, etc.  If nothing else, it will help folks from other teams understand who’s doing what.

3. Specify Methods & Parameters

The most important thing about your practice of agile is how you evolve it based on experimentation (not picking the rightest, truest methodology). You can’t evolve your practice if you’re not being explicit about what practices you’re implementing vs. not implementing. If you’re tracking burndown (or not) note that, for example. If you’re working to visualize your actual, observed workflow with kanban, note that.

4. Note Systems

List all the the major things you do as a team and what systems you use for those jobs (even if some of those systems are a Google Doc). Maintaining a shared understanding about this is more important than particular tools and practices.

5. Define Conventions & Practices

Yes, agile values individual interactions over processes and tools. That doesn’t mean it’s a good for team members to constantly hunt around for what they need because everyone does their work differently. If the team agrees a practice is important, it’s probably a good idea to agree to a shared view of conventions, even if they’re all under probation as an experiment.

6. Log Changes

Keeping a brief change record is probably a good idea so that if you have a question about why you did something or how a certain set of outcomes correlated with practice, you have an answer.

No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Ideas for Remote Retrospectives that Engage

Ideas for Remote Retrospectives that Engage | Devops et agilité | Scoop.it
Retrospectives have been shown to be an important tool for teams to improve their ways of working and increase collaboration. In person, retrospectives are well understood with many approaches and techniques. This article looks at how to carry the practice across when working remotely.
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Finastra lance son hackathon 2020

L’échéance pour soumettre un projet est fixée au 22 novembre 2020, et les gagnants seront annoncés en décembre, après avoir été évalués en direct.

Startup For Kids, une entreprise de l'économie sociale et solidaire, qui a pour but d’initier les enfants au monde de la technologie, soutiendra - avec les mentors d'Accenture - un volet distinct de "hackathon" pour les enfants, où les jeunes âgés de 10 à 18 ans pourront participer et soumettre leurs idées pour lutter contre les discriminations systémiques par vidéo et présentations, contribuant ainsi à un monde meilleur (aucune compétence en codage requise).

Vous pouvez vous inscrire dès aujourd'hui ici, et commencer à hacker pour un avenir meilleur, ou rejoignez la conversation sur les réseaux sociaux en utilisant #HackToTheFuture et #HackingForGood.
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Le métier de coach en management

Le métier de coach en management | Devops et agilité | Scoop.it
Entre analyse et formation, quelles sont les missions d'un coach en management ? De la start-up au grand groupe en passant par la PME, focus sur ce métier.
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Un guide DevOps autour de Docker, Kubernetes, Ansible, Linux ...

Un guide DevOps autour de Docker, Kubernetes, Ansible, Linux ... | Devops et agilité | Scoop.it
Découvrez un guide DevOps traitant de Docker, Kubernets, Ansible, Linux. Ce guide part du niveau basique à avancé et comprend des interviews et des notes.
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Coach Agile Scrum | Freelance-Informatique

Coach Agile Scrum | Freelance-Informatique | Devops et agilité | Scoop.it
Entreprises, SSII : trouvez rapidement un coach agile scrum disponible sur notre plateforme freelance ou déposez une offre de mission.
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Besoin d’un Coach Agile freelance ?

Besoin d’un Coach Agile freelance ? | Devops et agilité | Scoop.it
Qui sont les Coachs Agile inscrits sur Coworkees ?
65% sont des hommes
42 ans d'âge moyen
6 ans d'exp. en moyenne
Taux journalier moyen d’un Coach Agile freelance
Junior 476 €
Intermédiaire 654 €
Confirmé
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

x-matrix / matrice en x du Hoshin Kanri

x-matrix / matrice en x du Hoshin Kanri | Devops et agilité | Scoop.it
x-matrix, comment mettre en oeuvre et utiliser efficacement la matrice en x au sein du processus Hoshin Kanri. Conseil, formation, accompagnement.
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Software Craftsmanship and Empowerment- Agiilemnaia

Software Craftsmanship and Empowerment- Agiilemnaia | Devops et agilité | Scoop.it

Why do we need a software craftsman?

  • The best processes in the world will not save a project from failure if the people involved do not have the necessary skills to execute the process; conversely, really good developers can make any process work” – Pete McBreen, Software Craftsmanship: The New Imperative
  • Because crappy code amplifies the risk of failure – even for agile projects
  • ”Get It Done” vs. ”Get It Right”
  • A Software Craftsman will choose “Get It Right” because he has the skills to do so
  • Not only will he “Dot It Right”, but he will also do it for the right reason
Mickael Ruaus insight:

Characterization of a Software Craftsman

  • He will “Do It Right” – also under pressure
  • He takes responsibility
  • He takes pride in his work. Both the end product and the process towards it
  • He signs his work
  • Software Craftsmanship is all about putting responsibility and pride back into the software development process. As Hunt and Thomas (The Pragmatic Programmer) state, we need to start ‘signing our work’ again, just as other craftsmen do” – Pete McBreen, Software Craftsmanship: The New Imperative
  • He is a continuous learner. When he doesn’t work, he spends his time studying, to find new methods and tools can refine him as a Software Craftsman
  • He writes code
  • He practices deliberately and understands the difference between practice and work. He practices in order to be prepared for work
  • He has the right attitude towards Software Development
  • He contributes to the community

How to become a Software Craftsman by following some discipline [Best practices]?

  • Test-Driven Development [TDD]
  • Continuous Integration
  • Pairing
  • Pride and attitude that QA should find nothing
  • Refactoring
  • Iterate always with shorter time boxing to get multiple feedbacks
  • Tips from The Pragmatic Programmer
    • Care about your craft
    •  Think about your work
  • Practices lot of industry-accepted engineering practices
  • Automate as much as possible
  • Start learning
  • Take responsibility for your professional career and apply what you’ve learned
  • Slow down to go fast
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Pour une ANALYSE DE LA VALEUR avec les concepts de Value Stream et Ca…

Avec la version Archimate 3.1 , la couche de stratégie comporte 2 objets de modélisation majeurs de l’analyse de la valeur : Value Stream & Capability. Ce docu…
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Free Agile Team Charter Template

Free Agile Team Charter Template | Devops et agilité | Scoop.it
Sample Agile Team Charter

Below is a sample Team Charter for an Agile project. Again, while there is no standard template for what should/should not be included, this represents a general approach and good starting point. Based on the project type, team experience, and organizational standards, this sample may be adjusted as necessary to accomplish your team’s specific intent.
Mickael Ruaus insight:

Project Name: Invoice Tracking Database

Vision: Help the billing department reduce the number of monthly past-due accounts by providing an easy to use platform for tracking accounts receivable.

Mission: Create an invoice tracking database that enables billing employees to view real-time account statuses, engage vendors proactively to resolve accounts, and generate weekly and monthly account reports.

Success Criteria:

  1. Implement database by March 1, 20xx
  2. Reduce monthly past-due accounts by 75% after 3 months
  3. Achieve > 80% favoriability among billing employees via survey after 3 months

Project Team

Name Role Phone A. Black Product Owner (555) 555-1111 B. White Scrum Master (555) 555-2222 C. Green Programmer (555) 555-1414 D. Teal Database Administrator (555) 555-3333 E. Gray Network Administrator (555) 555-1515 F. Brown Billing Coordinator (555) 555-4444

Rules of Behavior:

  1. All team members will treat each other with respect at all times
  2. Constructive feedback is a valuable part of our success so we will not take offense and all team members will ensure all feedback is provided in a constructive manner
  3. Open communication among the team is always welcomed and valued
  4. We will recognize and celebrate all individual and team accomplishments
  5. All personal cell phones will be turned off prior to beginning any of our meetings or discussions
  6. We will accept responsibility and be accountable for our actions
  7. We will give consideration to whomever is speaking and avoid sidebars or speaking over one another
  8. We will work collaboratively when possible and use a consensus approach when making team decisions

Communications:

  1. We will hold regular daily meetings in the team room at 9am each work day
  2. We will make every effort to attend all scheduled meetings in person (exceptions being scheduled and/or sick leave)
  3. We will update our tasks on the kanban board each work day morning before 9am
  4. Meeting minutes will be sent out within 24 hours of each meeting
  5. The responsibility for meeting scribe will be shared by all team members on a rotating basis
  6. If a meeting must be cancelled or additional meetings are required, the Product Owner will send out notifications as early as possible
  7. All team members are expected to be on time for all meetings
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

The Agile Inception Deck

The Agile Inception Deck | Devops et agilité | Scoop.it
Download Blank Inception Deck

Online course Udemy

One area most agile methods are completely silent on is project chartering. Below is a lightweight you can use to fill this gap and get your project headed in the right direction long before the first line of code every gets written.
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

The Team Charter - build a better team together | Bigger Impact

The Team Charter - build a better team together | Bigger Impact | Devops et agilité | Scoop.it
The Team Charter is a simple tool for building a better team by jointly deciding how you’re going to work together.
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Agile Grenoble 2019: Le craftsmanship - la pièce manquante de...

No comment yet.
Scooped by Mickael Ruau
Scoop.it!

La stratégie Software Craftsmanship / Devops

La stratégie Software Craftsmanship / Devops | Devops et agilité | 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
No comment yet.