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.
Are you planning to hire a consultancy company to start your Agile Transformation? If yes, you must read this post and do some homework first
When hiring an Agile Transformation Consultancy company it would be good to have clear why are you doing it, what do you expect to achieve with it in the business goals perspective and in the company culture too. Based on your goals and time to reach them, it would be great to organize an interview asking to
(Cabanas Beach, Portugal) A lot was written already in this blog about why we have more advantages adopting Agile methods. The truth is, once an organization decides for an Agile Transformation, adopting Agile methods and, particularly Scrum practice, to train and educate resources can be a terrifying challenge. Even with training, the roles will change.
(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
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 🙂