It’s about time we close working cycle times in our LPM project management. In the previous newsletter we described the evolution of sprint progress through the sprint planning and the daily meeting. We have not elaborated on how the release progresses since this is based on the progress of the Sprints that compose it. To conclude each of the sprints … Read More
In our news last month we explained that we would manage projects moving in cycles: Releases and Sprints. We also reviewed the Release Planning and how we developed the Release Backlog, which is the list of tasks to perform to achieve the Release. Going in detail into the Release, we see it is split in Sprints. These are short cycles … Read More
At this point in time during summer in the hot Spain, we should be enjoying icy drinks instead of talking about burn downs, but you already know what is our preferred recipe to manage innovation: discipline, discipline and discipline. Therefore we continue with our LPM series and its “burning” artifacts. First of all, and after talking in our July news … Read More
In the previous news we introduced the Sprint Backlog as the list of tasks to be done during the different sprints. These tasks are detailed and assigned during each specific Sprint Planning Meeting. In this month’s news we will see what kind of artifacts are available for the process of assigning tasks to the team members. There are two steps … Read More
In the February newsletter we covered the LPM concepts of roles, artifacts and processes. Since then, we have discussed in detail the roles that play in this methodology. Now it is time to penetrate the artifacts. Artifacts are the tools used in order to support and facilitate how a Project is managed. We start with the two backlogs: the Product Backlog and the Sprint Backlog. A backlog is a list or … Read More
In our two previous newsletters we introduced the roles of Product Owner (representing the client) and the Scrum Master (responsible for the correct application of the LPM process). To complete the area of roles in our LPM methodology, we will talk here about the third role in LPM – the Team.
In our previous newsletter we introduced the role of Product Owner, who –as you recall– represents the client wanting the product or service. Continuing with the roles that participate in our LPM methodology, today we will talk about the role of Scrum Master.
Let us introduce the role of Product Owner within the roles distribution in Lean Product Management (LPM). This role represents the client who commissions the project. It is responsible to ensure that the final result of the work performed by the team meets the client’s expectations.
As promised, we are coming back to the who is who in Lean Project Management, ready to do it in a “lean” way. Let us know if we abuse the theory and fail in our endeavor.