#Agile
34 notas · última:
Vamos falar sobre Story Mapping
O texto explica como o Story Mapping ajuda a priorizar o backlog, definir releases e alinhar expectativas. O método organiza fluxo, épicos, histórias e objetivos para facilitar entregas de valor.
Organizational Agility
The post argues that Agile should not be confined to IT. It says true agility comes from fast feedback, shared values across the organization, clear vision, trust, and self-managing teams with the authority to act.
Agile Spikes Deliver Knowledge So Teams Can Deliver Products
Spikes are time-boxed research work that helps agile teams reduce excess uncertainty, make better decisions, and learn enough to deliver features later without using spikes too often.
Why Developers Are Poor Testers and What Can Be Done About It
The page says developers often test poorly because they protect their own code, simplify problems, miss small flaws, focus on happy paths, and lack user perspective. It then suggests ways to improve testing.
How To Choose The Best Agile Framework For Your Team
The text compares Scrum, Kanban, Scrumban, XP and FDD, highlighting how each framework organizes work, collaboration and delivery. It also shows how Assembla supports planning, tracking and release.
Frank - How are you so productive?
The post frames productivity as maximizing value while balancing effectiveness and efficiency, then presents practical habits like prioritization, Kaizen, time boxing, focus, and escalation.
Lean Software Development; Make More Money
The text presents the lecture “Make More Money” by Mary Poppendieck, describes her experience in operations and new product development, and mentions the book Lean Software Development: An Agile Toolkit.
Prioritizing user stories in agile product management
Walks through MoSCoW and RICE as the two dominant methods for prioritizing a product backlog, and argues each fits a different stage of a product's life.
Manifesto for Deadline Driven Development
The text contrasts deadline-driven habits with Agile technical practices, arguing that tests, clean code, refactoring, CI, and ATDD are what make incremental delivery and fast feedback possible.
Non-Technical Frontend Interview Questions
The article collects non-technical frontend interview questions about product thinking, Agile, and soft skills, and offers example ways to answer them in interviews.
How to Cultivate Agile Servant Leadership
The page explains how servant leadership fits Agile and how project managers can use listening, empathy, persuasion, and stewardship to guide organizational change and support team autonomy.
Métricas para Projetos Agile #4
O texto explica por que medir WIP ajuda a enxergar gargalos, prever capacidade e reduzir trabalho quase pronto, e defende limites de WIP para melhorar o fluxo do time.
Métricas para Projetos Agile #2
O texto explica lead time em desenvolvimento de software, distingue-o de cycle time, mostra três formas de ler sua distribuição e sugere práticas para reduzir variabilidade e acompanhar entregas.
Métricas para Projetos Agile #1
O texto defende métricas como meio de entender, controlar e melhorar o processo de desenvolvimento, com foco em autogestão, melhoria contínua e visibilidade da saúde do time.
Building A Real-Time Retrospective Board With Video Chat
The article shows how to build a virtual retrospective board with deepstream, using records and lists for sticky notes, real-time sync, password login, and WebRTC video chat.
Modernising legacy code with SOA and Agile
The article describes how a legacy Delphi CRM was modernised without a full rewrite by translating some code, adding new services through SOA, and using Scrum to stabilise priorities and delivery.
Why software is a craft [and also an industry]
Software development is presented as neither pure craft nor fully rule-driven industry. It needs basic methods and planning, but still depends on context, judgment, and adaptation as unknowns appear.
Principles for programming beautiful code
The article argues that code beauty is hard to define, but points to integrity, usability, innovation, and brevity as qualities that can make software and the process around it feel beautiful.
Overcome Agile hangovers with a 'software craftsman' approach
The article says Agile often disappoints when teams focus on process instead of software quality. It argues for a software craftsmanship mindset centered on technical excellence, customer needs, and better respect for developers.
Developers Shouldn’t Measure Twice, Cut Once
The post argues that the “measure twice, cut once” rule fits construction, but not software work. In programming, rough estimates and early coding are more useful than long planning and estimation meetings.
[RailsConf 2010] - Video Entrevista - Robert Martin
A entrevista de 16 minutos com Robert Martin aborda evolução das linguagens, ciclos de vida das linguagens, aprendizado contínuo, Agile, Scrum, certificações e a origem do Manifesto Ágil.
6 Practical Agile Techniques You Can Start Using Today
The article argues for small Agile changes that improve speed, quality, and communication: deliver more often, involve testers in requirements, write user stories, use prototypes, and think about testing early.
So You Really Want to be an Agile Developer?
The page contrasts faux Agile with the manifesto’s intent and argues that full-on Agile means the development team collectively owns requirements, testing, planning, coordination, and other responsibilities.
Agile Is Dead (Long Live Agility)
Dave Thomas argues that “agile” has been emptied out by consulting, marketing, and misuse as a noun, and that software teams should return to the manifesto’s values as practical agility.
8 reasons Lean IT now really matters to enterprises
Steve Bell argues that Lean IT helps Agile scale in larger enterprises by tying technology to customer value, making innovation routine, handling uncertainty, and cutting waste in ERP and prioritization.
[Off-Topic] Agile feito Errado
O texto argumenta que Agile não corrige maus profissionais nem liderança fraca. Sem capacidade técnica, disciplina e responsabilidade, práticas como planning, pair programming e qualidade viram distorções.
Self-Organizing Organizations (For Real)
The article describes how /ut7 runs as a self-organizing co-operative without managers, using open meetings, pair work, transparent finances, and shared responsibility while rejecting preset models and shared vision exercises.
Como calcular pontos em uma Sprint?
O texto explica duas formas de estimar quantas estórias cabem em uma Sprint, usando velocidade passada ou fator de foco, e mostra como isso limita o backlog para evitar promessas acima da capacidade.
Minimum Viable Products for Enterprises
The page compares ideas of MVPs for enterprise software, showing how lean startup, buyer-user separation, feature-heavy buying habits, and stakeholder patience make the enterprise case different from consumer products.
Dividir para conquistar no desenvolvimento de software
O texto relaciona produtividade em software à entrega de valor ao cliente e defende dividir a demanda em partes menores para encontrar o ponto em que cada entrega gera valor mais rápido.
Programação em par
A programação em par é apresentada como prática do XP que reduz bugs, melhora o foco, acelera decisões e dissemina conhecimento, embora peça humildade e adaptação inicial.
Risco e desperdício em projetos Agile
O texto argumenta que equipes Agile precisam identificar riscos cedo e medir quando vale investir em qualidade, porque tanto o design adiado quanto o excesso de testes podem gerar desperdício.
Effective Steps to reduce technical debt: An agile approach
The post outlines a pragmatic agile way to reduce technical debt: involve the product owner, map known issues, estimate them relatively, and fold repayment into daily development.
Você não entende nada de Scrum
O texto liga Scrum a auto-organização, complexidade, caos e gestão do conhecimento, defendendo que práticas ágeis só fazem sentido com estudo de princípios e evidências.