Skip to main content

Make work visible

To make work visible for an Agile team using Scrum or Kanban, you can use the following techniques:

Scrum:

    Use a Sprint Backlog: This is a prioritized list of tasks that the team needs to complete during the sprint.
    Use a physical or virtual task board: This board displays the state of each task and is updated regularly by the team members.
    Use Burn-down charts: These charts help to track the team's progress and identify any issues that may be preventing them from completing work.

Kanban:

    Use a Kanban board: This board displays the state of each task, and tasks are moved from left to right as they are completed.
    Use Visual signals: Use color-coded cards or sticky notes to show the state of each task and identify any issues.
    Limit Work-in-Progress: Set limits on the number of tasks that can be in progress at any given time, to focus the team on completing work.
Regardless of which methodology is used, it's important to keep the board updated regularly and to make sure that the entire team has access to it. This helps to keep everyone informed of the team's progress and ensures that everyone is working together towards the same goal.

Comments

Post a Comment

Popular posts from this blog

Navigating Chaos: The Cynefin Framework for Engineering Managers in Startups

In the fast-paced world of startups, engineering managers often find themselves grappling with complex problems, uncertain environments, and rapidly changing circumstances. It is in such chaos that the Cynefin framework, a sense-making model, can offer valuable guidance. By understanding and leveraging this framework, engineering managers can effectively navigate the intricacies of their roles, make informed decisions, and foster innovation within their teams. The Cynefin framework, developed by Dave Snowden, provides a toolset to analyze and make sense of complex situations. It offers five domains that represent different types of problems: Simple, Complicated, Complex, Chaotic, and Disorder. Each domain requires distinct approaches and strategies for problem-solving. Let's delve into each domain and understand their implications for engineering managers. Disorder Domain The disorder domain represents a state of confusion and ambiguity, where the nature of a problem is unkno...
Post a Comment
Read more

What is your leadership style?

I have been asked this question in all interviews for roles that have lead, mentor and coach other engineers or stakeholders. The only place I haven't been asked this question was at a startup where I was supposed to manage engineers. One of the main reasons that it wasn't asked is that the Engineering Manager role is not well defined there. I had to learn this fact in a painful way at the end. So what are the different leadership styles for a manager? There might be more but I have come across the following basic ones Leadership is an important aspect of any organization or society. Leaders are responsible for guiding their followers towards a common goal or objective. There are many different leadership styles, each with its own strengths and weaknesses. In this blog, we will explore some of the different leadership styles, with instances from mythology. Autocratic Leadership Autocratic leadership is a style in which the leader makes all decisions without input from ...
Post a Comment
Read more

Agile Cooking: Backlog Grooming, Planning, and Execution with a Dash of Leftover Magic

Introduction: Agile development methodologies have revolutionized the software industry, enabling teams to deliver high-quality products in a flexible and efficient manner. But have you ever wondered if the principles of agile could be applied outside the realm of coding? Surprisingly, meal making shares many similarities with agile development, particularly in terms of backlog grooming, planning, and execution. In this blog post, we will explore how these two seemingly unrelated fields converge, and how leftover food management can be analogous to waste management in agile projects. Backlog Grooming: From Ingredients to Task Prioritization In agile development, backlog grooming involves refining and prioritizing the tasks needed to achieve project goals. Similarly, meal making begins with identifying the ingredients available. Just as developers assess the value and complexity of user stories, cooks evaluate the ingredients' freshness, taste, and compatibility to decide ...
Post a Comment
Read more