People usually laugh when I tell them my kids have Kanban Boards and Social Contracts.
This is a post about how my Family has adopted the Agile Mindset, Agile Practices and has become an Agile Family.
Mom, Dad, 3 kids and 3 pets — one dog and two cats.
When all this started, our kids were 6, 4 and just a baby.
Today they are almost 10, 7 and 3. ❤
It’s been more than 3 years now since I first considered the possibility of adopting Agile at home.
Like today, I was an Agile Coach then, leading the transformation…
…So What is a #ProductOwner (PO)?
A PO is responsible for maximising the value of the product, or the value delivered to the customers and the business, resulting from the work done by the Development Team.
The Product Owner is the sole person responsible for managing the Product Backlog. TheProduct Backlog is the Product Owner’s tool and he or she is the ultimate responsible for it.
Managing a Product Backlog, usually includes:
It usually happens:
Typically, individuals on the team may answer 3 questions to get them going:
Planning Meeting is the ceremony in which a Team plans and agrees on the User Stories or Backlog items they would like to deliver on the next iteration / sprint (which may vary between 1 and 4 weeks).
This is the ceremony where the Team also discusses and identifies the tasks as well as tests for delivery and acceptance.
Planning meetings usually happen at the beginning of each iteration, and it usually takes 2 hours for every week of iteration.
Retrospectives is an Agile ceremony; a practice used by teams to reflect on their way of working, and to continuously become better in what they do; iteration after iteration.
It is not about WHAT they deliver; but HOW they deliver things and what can be improved about it.
Agile Words! Agile Learning! Being Agile! :)
This is an #Agile ceremony that is held near the end of one iteration to ensure the backlog is ready for the next iteration.
During a product backlog Refinement Meeting, the #team and #product #owner discuss the top items on the product backlog. The team is given a chance to ask the questions that would normally arise during sprint planning:
The idea of this post is to give you a template User Story, that you can copy, adjust to your needs, and re-use it as many times as you like.
As an Agile Coach, and someone actively working on changing people’s mindset and ways of working, as well as corporate culture; one of the things that I have been observing recently is how key it is to have good written user stories… they are the opener of your funnel of work and thus having it in good shape is key to drive a good workflow for your team and your…
Today’s post on my #LearningAgile series is about Release Planning.
Agile Teams use rolling wave planning and progressive elaboration, refining and adjusting plans at various points throughout a project’s life cycle.
Planning is beneficial because it reduces risk and uncertainty, improves decision making, fosters trust and makes it easier to pass information over to stakeholders and within the team.
During an Iteration Planning, the stories and features that belong to that specific iteration are broken down into specific technical tasks, or units of work, that can be assigned to particular developers.
Stories are often estimated in story points…
Today’s post will talk a little bit on how to track progress of a Sprint.
Scrum Teams use Burndown Charts to track the cumulative number of hours of work remaining in a Sprint or Project against the number of days remaining until the end of the sprint or the planned project deadline.
Scrum Teams may also use various progress charts, such as the Scrum Task Board to track the status of the tasks during a Sprint.
Find out more about these below:
We have already studied a little bit about Burndown Charts and its utility, earlier…
Today, I want to share a little bit about two Agile frameworks: Extreme Programming and Lean.
Extreme Programming, also known as XP, promotes the ongoing, rapid delivery of small releases of software. It is a collaborative system that relies on core values of communication, simplicity, feedback, and courage.
Its principles include collective ownership, continuous integration, energized work, use of a shared work space and the inclusion of an on-site customer.
Extreme Programming practices include pair programming, ongoing testing and refactoring, simple design, the planning game, and use of metaphor.
Lean development streamlines development, by encouraging teams to develop only the…