I am very glad to celebrate with you the 400 followers on the Instagram with an interview. The interview with Philip Becker could not be a more expressive celebration of this. Let’s see how in a context outside Software development, the use of Ageis methods motivates groups and improves efficiency.
Why should we estimate? What are we considering when we do it? Yes, estimation accuracy is a matter of practice maintaining the same team constant. What and how can we estimate? We can do it all over hierarchy of requirements, since strategic levels until implementation ones. But essentially a good product planning should be done
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.
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.
(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
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.
(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!
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 🙂