DEVOPS
Follow
Find
14.6K views | +14 today
 
Rescooped by Shaker technologies from Management and Agility
onto DEVOPS
Scoop.it!

'If You Can't Measure It, You Can't Manage It': Not True

'If You Can't Measure It, You Can't Manage It': Not True | DEVOPS | Scoop.it

hu

Fifteen years later I still find it weird that I sucked down so much nonsense working in the corporate world, lots of it without even noticing. I sat in workshops and seminars and heard the most patently ridiculous garbage shoveled at me and the other participants, year after year for [...]

Via Philippe Vallat, Pascale Mousset
Shaker technologies's insight:

We focus on the particles when waves are swelling and crashing all around us.

Great employees and great leaders manage the waves all the day, unmeasured and too often unseen. They manage customer relationships in the moment and over the long term. How do they do that so well, without benefit of yardsticks to guide them? How do they finesse and intuit and consult their way to the brilliant results they achieve, without the reports and tests that slow us down and annoy us in every other professional arena? Thank God, human processes like sticky conversations and the energy in a classroom or a conference room can’t be measured.

Those human waves have to be felt.

more...
Damien Thouvenin's curator insight, February 12, 2014 1:41 AM

Déconstruction d'un mythe du management mais aussi, et de manière plus intéressante, des raisons profondes qui font que nos organisations continuent d'entretenir ce mythe.

Illustrations sympas, en prime :-)

Miklos Szilagyi's curator insight, February 13, 2014 3:49 AM

I actually love this...:-))) one of the bullshittiest of all...  The "M" from the SMART... which does not mean that SMART is not a good yardstick-model... it's good to help to structure your thinking process... the same thing for performance appraisal methods... they are good framework... but, please, don't take them too on face value, too seriously...

 

The same thing about all these test-mania in the schools and everywhere... that's the moment for me (excellent article, that's  courage...) to say that the earlier methods, writing and oral (!!!) exams were much more effective, OK, more subjective but at the end of the day, we are human and could be something more subjective than a human being?! Why do we try to hide this, fear of this? And try to robotize it? By that we are just stripping from all these processes  the only interesting part, the "human" element... They are dead seriously objective, only,  they are good for nothing or very very little...

 

Aline Choupin's curator insight, February 24, 2014 9:35 AM

Liz completly nailed it !

DEVOPS
DEVOPS, agilité, tests, déploiement, sécurité
Your new post is loading...
Your new post is loading...
Scooped by Shaker technologies
Scoop.it!

The Architecture of Open Source Applications

The Architecture of Open Source Applications | DEVOPS | Scoop.it

Architects look at thousands of buildings during their training, and study critiques of those buildings written by masters. In contrast, most software developers only ever get to know a handful of large programs well—usually programs they wrote themselves—and never study the great programs of history. As a result, they repeat one another's mistakes rather than building on one another's successes.

Our goal is to change that. In these two books, the authors of four dozen open source applications explain how their software is structured, and why. What are each program's major components? How do they interact? And what did their builders learn during their development? In answering these questions, the contributors to these books provide unique insights into how they think.

If you are a junior developer, and want to learn how your more experienced colleagues think, these books are the place to start. If you are an intermediate or senior developer, and want to see how your peers have solved hard design problems, these books can help you too.

Follow us on our blog at http://aosabook.org/blog/, or on Twitter at @aosabook and using the #aosa hashtag.

Shaker technologies's insight:

Buy Volume II

IntroductionAmy Brown and Greg Wilson1.Scalable Web Architecture and Distributed SystemsKate Matsudaira2.Firefox Release EngineeringChris AtLeeLukas BlakkJohn O'Duinn, and Armen Zambrano Gasparnian3.FreeRTOSChristopher Svec4.GDBStan Shebs5.The Glasgow Haskell CompilerSimon Marlow and Simon Peyton-Jones6.GitSusan Potter7.GPSDEric Raymond8.The Dynamic Language Runtime and the Iron LanguagesJeff Hardy9.ITKLuis Ibanez and Brad King10.GNU MailmanBarry Warsaw11.matplotlibJohn Hunter and Michael Droettboom12.MediaWikiSumana Harihareswara and Guillaume Paumier13.MoodleTim Hunt14.nginxAndrey Alexeev15.Open MPIJeff Squyres16.OSCARJennifer Ruttan17.Processing.jsMike Kamermans18.PuppetLuke Kanies19.PyPyBenjamin Peterson20.SQLAlchemyMichael Bayer21.TwistedJessica McKellar22.YesodMichael Snoyman23.YoctoElizabeth Flanagan24.ZeroMQMartin SústrikBibliography

Buy Volume I

IntroductionAmy Brown and Greg Wilson1.AsteriskRussell Bryant2.AudacityJames Crook3.The Bourne-Again ShellChet Ramey4.Berkeley DBMargo Seltzer and Keith Bostic5.CMakeBill Hoffman and Kenneth Martin6.EclipseKim Moir7.GraphiteChris Davis8.The Hadoop Distributed File SystemRobert ChanslerHairong KuangSanjay RadiaKonstantin Shvachko, and Suresh Srinivas9.Continuous IntegrationC. Titus Brown and Rosangela Canino-Koning10.JitsiEmil Ivov11.LLVMChris Lattner12.MercurialDirkjan Ochtman13.The NoSQL EcosystemAdam Marcus14.Python PackagingTarek Ziadé15.Riak and Erlang/OTPFrancesco CesariniAndy Gross, and Justin Sheehy16.Selenium WebDriverSimon Stewart17.SendmailEric Allman18.SnowFlockRoy Bryant and Andrés Lagar-Cavilla19.SocialCalcAudrey Tang20.TelepathyDanielle Madeley21.Thousand ParsecAlan Laudicina and Aaron Mavrinac22.VioletCay Horstmann23.VisTrailsJuliana FreireDavid KoopEmanuele SantosCarlos Scheidegger,Claudio Silva, and Huy T. Vo24.VTKBerk Geveci and Will Schroeder25.Battle For WesnothRichard Shimooka and David WhiteBibliography
License and Royalties

This work is made available under the Creative Commons Attribution 3.0 Unported license. Please see the full description of the license for details. All royalties from sales of these books will be donated to Amnesty International.

more...
No comment yet.
Scooped by Shaker technologies
Scoop.it!

Oracle met fin au support de Java 7, les utilisateurs invités à migrer vers Java 8

Oracle met fin au support de Java 7, les utilisateurs invités à migrer vers Java 8 | DEVOPS | Scoop.it
Oracle vient officiellement d'annoncer l'arrêt des mises à jour pour Java SE 7 (Standard Edition) dès la fin du mois d'avril 2015.
more...
No comment yet.
Scooped by Shaker technologies
Scoop.it!

Les développeurs Heisenberg - ticablog

Les développeurs Heisenberg - ticablog | DEVOPS | Scoop.it
Les développeurs Heisenberg Introduction Ce texte est une traduction de l’article de Mike Hadlow intitulée Heisenberg Developers pour laquelle il m' …
more...
No comment yet.
Scooped by Shaker technologies
Scoop.it!

Dear Dr. Use Case: What About Function Points and Use Cases?

Dear Dr. Use Case: What About Function Points and Use Cases? | DEVOPS | Scoop.it

Note: This is a summary of a recent discussion on the chat_rup forum. My thanks to the main discussion contributors: Davyd Norris, Pan-Wei Ng, and John Smith.

more...
No comment yet.
Scooped by Shaker technologies
Scoop.it!

Use Case Points App - Android app on AppBrain

Use Case Points App - Android app on AppBrain | DEVOPS | Scoop.it
Use Case Points is a simple and fast tool for help you to estimate de effort of software project development. The user interface is simple, fast and does the job of estimating the effort much easier.
more...
No comment yet.
Scooped by Shaker technologies
Scoop.it!

Are you too busy to improve?

Are you too busy to improve? | DEVOPS | Scoop.it

This illustration is inspired by and in part derived from the work by Scott Simmerman, "The Square Wheels Guy"  For translated versions of this image and terms of use please see this page 

more...
No comment yet.
Scooped by Shaker technologies
Scoop.it!

Are you too busy to improve? - Focus on the system

Are you too busy to improve? - Focus on the system | DEVOPS | Scoop.it

This illustration is inspired by and in part derived from the work by Scott Simmerman, "The Square Wheels Guy" For translated versions of this image and terms of use please see this page

more...
No comment yet.
Scooped by Shaker technologies
Scoop.it!

Scaling Agile in Large Enterprises: LeSS, DAD or SAFe? | Intland Software

Scaling Agile in Large Enterprises: LeSS, DAD or SAFe? | Intland Software | DEVOPS | Scoop.it
An overview of the frameworks that help scale Agile across large enterprises.
more...
No comment yet.
Scooped by Shaker technologies
Scoop.it!

La matrice des compromis : en cas de problèmes, qu’ajusterons-nous ?

La matrice des compromis : en cas de problèmes, qu’ajusterons-nous ? | DEVOPS | Scoop.it
Tweet This content is published under the Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported license. Tweet
more...
No comment yet.
Scooped by Shaker technologies
Scoop.it!

Trouvez les informations sensibles présentes dans votre boite mail - Korben

Trouvez les informations sensibles présentes dans votre boite mail - Korben | DEVOPS | Scoop.it

Si je vous parle de Dashlane aujourd'hui, c'est surtout pour vous montrer leur outil de scan qui permet d'aller analyser votre boite mail Hotmail, Yahoo, Gmail, AOL et faire ressortir tous les sites, dont le mot de passe en clair traine dans votre boite mail.

more...
No comment yet.
Scooped by Shaker technologies
Scoop.it!

«Génération de code pragmatique Java-web» - Témoignage sur : J'ai testé un outil de génération de code

more...
No comment yet.
Scooped by Shaker technologies
Scoop.it!

«Création à la souris d’une application Web sur mesure» - Témoignage sur : J'ai testé un outil de génération de code

more...
No comment yet.
Scooped by Shaker technologies
Scoop.it!

Les salaires des Devops seraient en hausse selon une récente étude, vers une meilleure reconnaissance ?

Les salaires des Devops seraient en hausse selon une récente étude, vers une meilleure reconnaissance ? | DEVOPS | Scoop.it
Les métiers du Devops seraient-ils en voie de devenir des profils de carrière technologique ?
more...
No comment yet.
Scooped by Shaker technologies
Scoop.it!

Comment garantir le succès d'un projet IT : top 5 des raisons pour lesquelles les projets informatiques échouent

Comment garantir le succès d'un projet IT : top 5 des raisons pour lesquelles les projets informatiques échouent | DEVOPS | Scoop.it
Il est plus facile de démarrer un projet informatique, mais garantir son succès est une chose moins évidente. Pour réussir, un projet doit se plier à des contraintes de coût, de délai et de respect des exigences définies par le cahier de charges.
more...
No comment yet.
Scooped by Shaker technologies
Scoop.it!

Scrumban: More Agile than Scrum or Kanban Alone? | Intland Software

Scrumban: More Agile than Scrum or Kanban Alone? | Intland Software | DEVOPS | Scoop.it
Scrumban combines Scrum and Kanban. Scrumban begins with Scrum and ends with Kanban. Scrumban is good for managing requirements and making us more Agile.
more...
No comment yet.
Scooped by Shaker technologies
Scoop.it!

Test Effort Estimation Using Use Case Points — Testing Excellence

Test Effort Estimation Using Use Case Points — Testing Excellence | DEVOPS | Scoop.it
Test Engineering covers a large gamut of activities to ensure that the final product achieves some quality goal. These activities must be planned well in advance to ensure that these objectives are met. Plans are based on estimations.
In the early years, the Waterfall model has been applied to software development. This model looks upon test engineering as merely a stage in the entire development lifecycle. When techniques evolved over the years for estimating development time and effort, the concept of estimating test-engineering time was overlooked completely.

Test engineering is seldom planned for in most organizations and as a result, products enter the market insufficiently tested. Negative customer reactions and damage to the corporate image is the natural consequence. To avoid this, the correct development lifecycle must be chosen and planning should be done
early on in the cycle.

Use Cases
A use case captures a contract between the stakeholders of a system about its behavior. The use case describes the system’s behavior under various conditions as it responds to a request from one of the stakeholders, called the primary actor. The primary actor initiates an interaction with the system to accomplish some goal. The system responds, protecting the interests of all the stakeholders. Different sequences of behavior, or scenarios, can unfold, depending on the particular requests made and conditions
surrounding the requests. The use case collects together those different scenarios.

Download the whitepaper
more...
No comment yet.
Scooped by Shaker technologies
Scoop.it!

How to Prepare Quotation Using Use Case Points - CodeProject

How to Prepare Quotation Using Use Case Points - CodeProject | DEVOPS | Scoop.it
Index
  • Introduction
  • Acronyms and Abbreviation
  • Assumptions
  • Scope
  • History and Definition of Use Case Points
  • Steps for UCP (Use Case Points) Estimation
  • Sample Project Scope (Sample Data Entry Project)
  • Writing Use Case for Sample Data Entry Project
  • Applying Use Case Points
  • Final Quotation
  • Use-Case Structure Matters
  • Advantages of Using Use-Case Points
  • Disadvantages of Using Use-Case Points
  • Other General Practical Factors
  • References
  • Last Words
Shaker technologies's insight:

"You can not plan if you can not measure, and if you fail to plan, you have planned to fail."


more...
No comment yet.
Scooped by Shaker technologies
Scoop.it!

Too Busy to Improve

Too Busy to Improve | DEVOPS | Scoop.it
"The number of people I meet who tell me, 'I don’t have time to make improvements to my work,' amazes me," writes Mike Orzen. But staying under water, always behind on work, doesn’t work either. Learn more about how to think differently about overwhelm and get ahead of the game.
Shaker technologies's insight:
  1. Work processes are either getting better or worse
    Left alone, processes atrophy and decline into a state of disorder due to the inevitable changes that occur and interdependencies along the value stream (think hand offs, conflicting priorities, and lack of visibility). Standard work is not sufficient to stem the tide of process degeneration.

  2. Unplanned work keeps us from improving
    Unplanned work is the work that eats away at whatever discretionary time we think we might have. Primary sources of unplanned work include rework, variation, break downs in the flow of information and materials, overburden, ill-defined work processes, and the unforeseen surprises that stem from conflicting priorities and a lack of transparency of the work (backlog and work in processes).

  3. Small improvements add up to big improvements
    Small changes in our work are also more sustainable. For example, it’s better to consistently practice your improvement work for 15 minutes a day, than to begin with the intent of spending an hour a day and then abandoning your commitment after a week from failing to find a free hour in your day. Daily practice is the key thing here. Aim for 40 consecutive business days of a new practice to create a habit. We tend to get good at what we consistently think about and do!

  4. There is tremendous influence in making things visible to our peers. 
    Creating a simple board that shows the date, topic, action taken, and next step(s) can be a game changer. A quick glance at such a board can quickly tell others what work is happening, what’s going well and what’s going wrong, and whether or not daily improvement work is taking place. This step takes courage, because you are making your commitment to process improvement public. But it also works because no one likes to make a commitment and not follow through.

  5. To change behavior, you need a routine
    You can’t improve if you don’t have a daily practice dedicated to improving. Thankfully, you don’t have to discover an effective routine and thought process to support a move towards daily improvement. Mike Rother’s gift to us all is Toyota Kata. This book skillfully explains the activities of daily problem solving, improvement routines that can be practiced and mastered, and the critical coaching element essential for developing people and creating internal problem-solving capacity. If you have not read this book – I highly recommend it.

In the end, though it may sound counterintuitive, dedicating time to daily process improvement is the only way out of the trap of feeling like you have no time. The only way to free up time to do more important work is to begin to chip away at the sources of firefighting and rework that are generating unplanned work.

more...
No comment yet.
Scooped by Shaker technologies
Scoop.it!

Team’s adaptability and experience are the key for success with Agile and Kanban | Intland Software

Team’s adaptability and experience are the key for success with Agile and Kanban | Intland Software | DEVOPS | Scoop.it
Adaptability and Experience are key to success with Agile and Kanban. In a survey among experts carried out by Intland Software, the following question was
more...
No comment yet.
Scooped by Shaker technologies
Scoop.it!

A Case for Agile Marketing – Beyond Software Development

A Case for Agile Marketing – Beyond Software Development | DEVOPS | Scoop.it
In the modern era of Customer Experience focused businesses, our internal processes for managing workloads needs to be continually evolving. Our teams are more frustrated and less satisfied in their…
more...
No comment yet.
Scooped by Shaker technologies
Scoop.it!

Deux normes ISO pour le cloud

Deux normes ISO pour le cloud | DEVOPS | Scoop.it

Une vue d’ensemble : ISO/IEC 17788

Un peu de vocabulaire tout d’abord avec la première norme. L’ISO/IEC 17788 donne la définition des termes les plus communément employés dans le secteur. On y trouvera notamment les différentes catégories de services existantes (logiciel en tant que service - modèle SaaS, plateforme en tant que service - modèle PaaS, infrastructure en tant que service – modèle IaaS). La norme éclaircit également les modèles de déploiements possibles et précise la distinction entre cloud privé et public.


L’architecture de référence : ISO/IEC 17789

La seconde norme rentre davantage dans la technique. Bardée de schémas et descriptifs détaillés, elle explique en un peu moins de 60 pages le fonctionnement d’une infrastructure cloud ainsi que les liens et articulations entre ses composants. L’objectif est de créer une architecture de référence qui servira de base commune pour les fournisseurs de manière à faciliter par la suite l’interopérabilité des services.

more...
No comment yet.
Scooped by Shaker technologies
Scoop.it!

Acceleo

Acceleo | DEVOPS | Scoop.it
Eclipse is probably best known as a Java IDE, but it is more: it is an IDE framework, a tools framework, an open source project, a community, an eco-system, and a foundation.
more...
No comment yet.
Scooped by Shaker technologies
Scoop.it!

AndroMDA Model Driven Architecture Framework – AndroMDA - Homepage

AndroMDA is an open source code generation framework that follows the Model Driven Architecture (MDA) paradigm.
more...
No comment yet.
Scooped by Shaker technologies
Scoop.it!

Spring Roo - Wikipedia, the free encyclopedia

Spring Roo

Spring Roo's mission statement is to "fundamentally improve Java developer productivity without compromising engineering integrity or flexibility". The technology was first demonstrated during the opening keynote at the SpringOne Europe developer conference on 27 April 2009, with an initial alpha release concurrently being published.

more...
No comment yet.
Scooped by Shaker technologies
Scoop.it!

Comparatif de générateurs de code | moins52, le blog

Comparatif de générateurs de code | moins52, le blog | DEVOPS | Scoop.it
Comparatif de générateurs de code, solutions MDA/MDD
more...
No comment yet.