Release Train: Release on a set interval of time, like trains departing on a regular schedule. Developers choose which train to catch when they have completed their feature.
Lots of our people have lots of opinions. Here are just a few of them
ThoughtWorks embraces the individuality of the people in the organization and hence the opinions expressed in the blogs may contradict each other and also may not represent the opinions of ThoughtWorks.
Branching Patterns: Release Train
festa de Pré-Lançamento do livro Diagrama de Fluxo Cumulativo
Festa de Pré-Lançamento do livro Diagrama de Fluxo Cumulativo O que: Palestra + livro Diagrama de Fluxo Cumulativo do Paulo Caroli Quando: Segunda, dia 25/05 às 19h Onde: devido ao COVID-19, o evento será online e as informações de acesso serão divulgadas no dia do evento. Por que: para bater papo sobre parâmetros de fluxo, […]
The post festa de Pré-Lançamento do livro Diagrama de Fluxo Cumulativo appeared first on Caroli.org.
Branching Patterns: Environment Branch
Environment Branch: Configure a product to run in a new environment by applying a source code commit. This pattern is a bad smell, only useful as a jerry-rigged mechanism for an application lacking that design, but then should be a high priority for removal with a sustainable alternative.
How to plan an inception?
You have to plan an inception and you are looking for activities to build your inception agenda. You reached the right page. But before going into many options for inception activities, let me start by answering this question: How to plan an inception? You have to sort out the people, the agenda, the place (physical […]
Well, Not so well and New ideas
Branching Patterns: Maturity Branch
A branch whose head marks the latest version of a level of maturity of the code base. Maturity Branches are usually named after the appropriate stage in the development flow. Hence terms like "production branch", "staging branch", and "QA branch".
[Sprint a Sprint] O mais vendido em 3 categorias!
A Mary e eu estamos extremamente satisfeitos e agradecidos. O livro SPRINT A SPRINT se tornou … olha que legal! … o livro nº 1 da Amazon em TRÊS categorias – Design de software, Computação, internet e mídia digital e Mudança Organizacional! Ficamos extremamente satisfeitos de receber comentários e resenhas sobre o livro (nossas timelines no […]
Branching Patterns: Integration Friction, Modularity, and some personal thoughts
I now finish off the integration patterns section of the article by describing the problem of integration friction, why modularity plays an important role when thinking of branching, and what kind of integration patterns I prefer to work with.
3-step prioritisation by impact and frequency
I have used the following 3 step prioritisation by impact and frequency many times, therefore I am sharing it on this post. I have learned it from Fabio Aguiar PBB’s book as he explain it in the context of prioritising Users Stories for building the product backlog. But I have used it in many instances, […]
What do you know about your advertiser?
Conserve or Invest?
Both the financial and real economies have suffered quite a few shocks in the last 20 years: the dot-com bubble bursting (2000); September 11 (2001); the Great Recession (2008); and today in 2020 the COVID-19 crisis is wreaking economic havoc. The crises have come with such frequency that executives leading companies impaired by the crisis already know the playbook: suspend the dividend, cancel any non-critical cash investments, negotiate with banks and bondholders to avoid defaults, pressure holders of hybrid securities to convert debt to equity, and progressively retrench business operations to reduced stages of life support. Uncertainty renders standard long-term…
Branching Patterns: Comparing Feature Branching and Continuous Integration
Feature Branching appears to be the most common branching strategy in the industry at the moment, but there is a vocal group of practitioners who argue that Continuous Integration is usually a superior approach.
Flexing to the demands of your team / Coaching for growth
Its about adapting your style to get the best out of your people to help them engage and to learn - to gain new skills and competence. Adapt to the growth of your team.
"adapt to growth" - lansberg
The Coaching SpectrumThere's a spectrum of choices of how to engage in coaching coversations
Software development teams find life can be much easier if they integrate their work as often as they can. They also find it valuable to release frequently into production. But teams don't want to expose half-developed features to their users. A useful technique to deal with this tension is to build all the back-end code, integrate, but don't build the user-interface The feature can be integrated and tested, but the UI is held back until the end until, like a keystone, it's added to complete the feature, revealing it to the users.
A simple example of this technique might be…
Branching Patterns: Integration Frequency
Integration Frequency has a huge impact upon a team's workflow. Higher frequency integration reduces the problems of complex merges, makes refactoring easier, and generally improves the communication and cohesiveness of a team.
Sprint a Sprint está na Amazon
Agora, o livro Sprint a Sprint está disponível na Amazon! >> Confira o livro Sprint a Sprint na Amazon, versões impressa e kindle. Muito obrigado pelo apoio e pelo feedback. As festas de pré-lançamento foram muito legais. Valeu pelo papo e pela comemoração, mesmo que remota. Vou convidar a Mary para uma live no […]