This is the first of a two articles series about the topic. I recommend to read this one first. Click here to open the second one. UPDATE June 2023 - I have also done some talks and workshops on this topic, like you can find in these slide deck. Introduction As many other graduates in … Continue reading Improve your software product delivery process performance using metrics (I)
Category: agile
If you want to go far, together is faster (II).
This is the second of a series of two articles describing the idea of correlating software product delivery process performance metrics with community health and collaboration metrics as a way to engage execution managers so their teams participate in Open Source projects and Inner Source programs. The first article is called If you want to … Continue reading If you want to go far, together is faster (II).
If you want to go far, together is faster (I).
This is the first of a series of two articles describing the reasoning and the steps behind the idea of correlating software product delivery process performance metrics with community health and collaboration metrics as a way to engage execution managers so their teams participate in Open Source projects and Inner Source programs. What you will … Continue reading If you want to go far, together is faster (I).
Agile On The Beach: my first time
During 2017 and 2018 I got several interesting references at events like Scale Summit and pipelineconf about an interesting event in the south-west of England about lean, agile and continuous delivery that got my attention. I decided that I could not miss it in 2019. 2019 edition of Agile On The Beach was the 9th … Continue reading Agile On The Beach: my first time
Bitacora: impact mapping
Introduction This is the fourth of a series of articles about Bitacora. Please read the previous ones to get full context: The diary (aka bitácora): towards alignment in distributed environment. Bitacora: environment definition. Bitacora: personas Why Impact Mapping? The steps taken so far are standard for me since long time ago. At this point though, … Continue reading Bitacora: impact mapping
Bitacora: personas
Introduction This is the third of a series of articles about Bitacora. Please read the previous ones to get full context: The diary (aka bitácora): towards alignment in distributed environment. Bitacora: environment definition. The environment description is incomplete without the personas. I like this concept for many reasons but the main one is because I … Continue reading Bitacora: personas
Bitacora: environment definition
Introduction This is the second of a series of articles about Bitacora. Please read the first one to get full context. In order to understand the perfect implementation of a Bitacora we need to go down the road of a product definition. One of the first steps is to define the environment. Bitacora is specially … Continue reading Bitacora: environment definition
The diary (aka bitácora): towards alignment in distributed environments
Article that introduces the concept of project/team/program journal/diary/bitacora
Apply agile methodologies to upstream development environments…. if you can.
IntroductionWhen the Agile Manifesto became popular and based on them, agile methodologies like Scrum, XP or Kanban, upstream development was in its early stages as collaboration ecosystems of companies.Only a few for profit organizations embraced developing upstream back then. Most of them were small and heavily influenced by FLOSS engineers vision. Free software communities were … Continue reading Apply agile methodologies to upstream development environments…. if you can.
Where the corporate and the upstream worlds meet…. or collide.
From the corporate world I frequently hear how hard it is to predict and track what upstream developers do. On the other side, developers that work part or full time upstream frequently underestimate the need for communicating what they do in a way that enable others (or themselves) to provide deadlines and effort estimations. Upstream … Continue reading Where the corporate and the upstream worlds meet…. or collide.