GO Product Roadmap Download. Unlike most product roadmaps, the GO roadmap is goal-oriented (hence the name).
Goals such as user acquisition, activation or retention play a central role. This shifts the conversation from debating features to agreeing on strategic objectives, making smart investment decisions, and aligning the stakeholders. The GO product roadmap is designed for creating products with Lean Startup or Scrum. Use it to establish product goals, carry out release planning, and coordinate the development and launch of different products. Training You can learn more about using the GO Product Roadmap by attending Roman’s Agile Product Planning Strategy and Roadmap course.
Please contact us for onsite delivery of the course, for bespoke product roadmap workshops, and for a virtual roadmap training course. Book.
Agile blogs. User Story Mapping Wall Skills. Scaled Agile. Agile article ideas. Agile tools. PRINCE2 Agile Practitioner Online Course (pre-order) Continuous Delivery. The Art of Splitting User Stories. Splitting stories—the act of breaking up large stories into smaller ones—is as much art as practice.
The strategy of splitting stories is to split them as late as possible to fit in a sprint just before the sprint that will take them on. Think of it as playing the classic arcade game Asteroids: you only want to break up the large asteroids when they are an immediate threat to you or when you've cleared out the smaller, more dangerous rocks…break up too many of them too soon and the resulting cloud of small asteroids will kill you. Similarly, if you break up a bunch of epics into a large number of sprint-sized stories, the resulting backlog bloat will cloud vision and diminish your response to change. There are a lot of good tips on how to split stories, like this one. In this post, I'm going to suggest some of the more common splitting techniques used for video game development. A couple goals exist for splitting stories:
Time Mgmt. PMI-ACP. Home. PMI. Agile Games. BPM. Kanban. Lean. Agile Analysis. Courses:itesm:fall_2011:tc4002:scrum_checklist_2011.pdf. Agile tools. Agile Governance. Agile Project Management Practitioner Training. The Japanese word "Kanban", literally means "Sign Card".
Kanban is the term borrowed by the software industry from the Toyota Production System. Kanban was one of the tools developed by Taiichi Ohno at Toyota. In its simplest form, it is the communication method that could be a card, an empty space, a cart, or any other signaling method to inform the upstream process that the downstream process to say that it is ready to receive next work item. Kanban method is rooted in its foundational Principles and Core practices. David Andersonâ€™s advice to implement Kanban method is to first follow the foundational principles and then adapt the core practices. Kanban foundational Principles are Start with what you do nowAgree to pursue incremental, evolutionary changeRespect the current process, role, responsibilities and titles Kanban Core Practices are 1.
Kanban is not a prescriptive approach. 2. Kanban method encourages continuous small incremental and evolutionary changes. 3. Visualise Yes. Yes. Waterfall, Agile & the “Triple Constraint” Anyone who has ever worked on a project probably realizes there are three (really four, but people often forget about the fourth) criteria that project success is focused on: 1.
Features (Requirements) 2. Estimates (Cost) 3. Schedule (Timeframe) 4. Quality (Often forgotten about since it is hard to see/define/measure) Regardless of whether we use waterfall or agile, we need to be concerned with these 4 elements. Normalized Story Points. I was recently involved in a discussion on LinkedIn on the topic of Normalized Story Points and whether or not it was a good idea.
What I noticed was that, despite what I think is a very clear explanation by the Scaled Agile Framework (SAFe), many people misunderstand both the process for normalizing Story Points and the intended benefit to be gleaned from this practice. If you have not yet, I encourage you to read the explanation in the “Iterations” abstract on the Scaled Agile Framework before reading on (the section entitled “Relative Estimating, Velocity and Normalizing Story Point Estimating”).
That will provide the proper context for my thoughts, as a Certified SAFe Program Consultant and active Release Train Engineer, on what this means (and what it doesn’t). First, how do we normalize Story Points? The gist of the process is this: “1. That’s basically it. This does not mean that teams are estimating using Ideal Man-Days. 41 Things You Need to Know about the Scaled Agile Framework® (SAFe) Comparing Scaled Agile Framework (SAFe) and Disciplined Agile Deliver… Make Product Decisions With A Practical Value Model. 2014 Agile Adoption Survey Results. Measuring Earned Value (EVM) on Agile and Scrum Software Development Projects. Click here to view the complete list of archived articles This article was originally published in the Fall 2007 issue of Methods & Tools Measuring Integrated Progress on Agile Software Development Projects Tamara Sulaiman, PMP, CST, SolutionsIQ, Hubert Smits, CST, Rally Software, Summary Earned Value Management (EVM) is a well known project management technique which measures the integration of technical performance, cost and schedule against planned performance within a given project.
Despite the benefits that can be gained, EVM techniques they have been slow to be adopted in the private sector, especially in the area of software development. Agile software development methods have been shown to be effective: software is developed faster, with higher quality, and better meeting changing business priorities and changing market conditions. Simon's Estimating Course.