(Berlin, Germany) Sometimes the most obvious Agile concepts are not so easy to be applied when we need to make a practical usage of them. Specially if we need to … Continue reading Requirements hierarchy, what should be written per level and by whom
A backlog is such an important asset for each Agile Team and even more important for a company who understands the value to demand for high quality content and well organized backlogs. What I would like to share with you today is a set learnings I did since I’m working in Agile.
Coming from my last post How abstract really are story points? I had the idea to share with you some websites where, completly free of charges, you can start your Agile Scrum estimation meetings.
(Düsseldorf, Alemanha) Estou no meu caminho de regresso a casa de fim de semana longo em Antuérpia, a cidade de Rubens, um centro logístico que foi reinventado ao longo do tempo, … Continue reading Portfolio Management: How can we capture and prioritize demand in a Lean and Agile approach?
Sometime it can be really a challenge to make a decision about which Proof of Concept should we develop out of the infinite number of feature we would like to add to our product.
Some time ago, a person told me “Marta I don’t like most of Agile coach because they are like religious radicals.” This week, in a Buddhist temple I saw this … Continue reading What does it mean to think Agile or Agile Thinking?
(In my way to Holidays) – During a long flight, I read about Greek mythology and I found it interesting and funny because I realized how Hercules, the Greek hero … Continue reading Kanban and the Greck Mithology
(Antwerp, Belgium) From the city where the concept of logistics has been reinvented over time, let's talk about why traditional portfolio management of you no longer has.
Today I write my reflections on this exciting issue of leadership of servers, from Antwerp (Belgium), in a Portuguese cafeteria:)
An Organization is described by the processes and structures that define the way people interact. But people has individual values that sometimes can to sabotage the organization evolution.
Retrospective meetings are recurring meetings that usually take place after the sprint review. These are very important moments to make a team think about what can be improved. But sometime there are moments when the team is faced with some difficulties in dealing with problems.
Sometimes when we are requested to present a Product Roadmap it is hard to start… Start from where? Which features? Which inter-dependencies? How to define priorities? Priorities in the order of the tasks or in the features to enhance product value? MOSCOW can help you 🙂