You will never turn back
I’m very happy to announce today our first Interview with Agile professionals!
I invited Mark Ansonia for our first interview with experts in Agile roles. Mark is a very experienced Scrum Master and Agile Coach, in this short interview he will share his experience among different projects and industries.
Continue reading “Interviewing Agile Professionals: Mark Ansonia”
We can explore those questions from different angles, but my simplified definition is: a team is a group of individuals moved by a common goal. Everything is better if, in the meantime we move together towards the goal, we share a positive energy and attitude in between the group.
Continue reading “What is a Team? What makes a Team?”
It’s always annoying when something comes up out of the plan and the team must fix it or manage it inside the sprint. Unfortunately, we must deal with unpredictability. Nevertheless, is always good to analyze why we had to deal with those annoyances.
What can be considered an annoyance? In my opinion, we can consider as critical bugs or unplanned change requests, we receive during the sprint or release and we must integrate or fix it within the sprint. In this post, we will approach, in a generic way some reasons for this and if it happens, who will report it into the backlog and which other measures should we consider to keep the sprint in a normal speed.
Continue reading “Annoyances: How to deal with critical issues, not planned, entering in the middle of the sprint or release”
The Product Owner role for a software product in an industry where the core business is not IT is a business enabler, a business transformation agent and an innovation partner. Someone who his success depends on the success of the business he supports. Sometimes it reminds me a marriage, an alliance.
In this post I would like to share my thoughts about the required skill set we should look for, when hiring one. Continue reading “If you are out of software industries and you are planning to hire and IT Product Owner, you must read this post!”
(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 bring into a consistent and common understanding a product or portfolio vision for later implementation. My goal with this post is to share a very personal opinion about how and whom should fulfill those Agile requirements levels.
Continue reading “Requirements hierarchy, what should be written per level and by whom”
A backlog is a very important asset for an Agile Team. It becomes even more important for a company who understands its value and is able to demand for high quality content and well organized backlogs.
Let’s try to understand what is a Backlog and all value behind this organized list of work by epics and stories shaping the product strategy.
Coming from my last post How abstract really are story points? I had the idea to share with you some websites where, completely free of charges, you get the necessary features to support your refinement meetings and estimation process.
Continue reading “Planning poker free of charges. Now you don’t have blockers to do your estimations”
(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 was already aware of the Kanban secrets 🙂 to achieve his challenges. Let’s speak about Kanban!
Continue reading “Kanban and the Greck Mithology”
Sometimes when we are requested to present a Product Road-map 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?