Have you or your Agile teams had trouble refining requirements on an Agile project? Are your teams struggling with user stories and tasks that are too large for them to handle well? If so, you and your teams need more guidance to implement backlog / user story grooming. Backlog grooming is a step-by-step process of taking high-level (“coarse-grained”) requirements and refining them to lower-level user stories and tasks (“fine-level”) that are ready to put into a sprint. In RefineM’s Backlog/Story Grooming presentation, attendees will learn how to work the process to achieve fine-grained requirements that are ready just in time. The key to success is leveraging tools and techniques as well as the expertise of your team to refine requirements iteratively.
85 items found
Gantt Charts are a fine mechanism for planning projects that have well bounded activities with a clean start and end point, and with understood dependencies and sequences. But in the non-linear, sometimes chaotic world of Product Development, Gantt Charts can be inadequate, cumbersome, or even misleadingly inaccurate. In the session, we will explore an alternative using mechanism of Agile product development - a Backlog of value to deliver with estimations of size (effort) and a reality-based Burndown that shows a plan with visible assumptions. Together these mechanism provide an effective way to plan, track, and replan a complex Product Development effort.
Many people claimed to have worked under a bad boss. Bad bosses are a top reason that good people leave a company, and they are bad for a company's bottom line. But what makes a bad boss? Is there a way to identify a bad boss? Is someone a bad boss, or do they simply communicate poorly? In this webinar, the presenter, Ryan Haag, walks you through his experiences with two particularly bad bosses and uses them as examples to help you identify bad bosses and to be able to work through them.
When one evaluates the project management body of knowledge, processes, procedures and common practice one cannot miss that the main focus and attention are placed on the planning processes. Most of PMI PMBOK is dedicated to planning processes, the project management process has only one step dedicated to execution and all the rest are planning steps.
In this talk I cover Why individuals & organizations need to be constantly on their toes and be ready to face the Future in the new BANI world. I will also list some of the tectonic changes an organization needs to make to not only survive but shine in the new world order.
Banking can be an overwhelming mystery of rules, acronyms and confusion! This talk is perfect for anyone who has just started working in a large Bank or other Financial Institution and needs help finding their way around...Experienced Financial Services Project Manager Jon McGowan, PMP will share with you his Visual Guide to navigating through these giant companies to help you become more successful in your new Project Manager role.
The purpose of the webinar is to give attendees a thorough understanding of how to create and use a CPM schedule to bring projects in on time, as well as understand some of the pitfalls of poor network design. If you are new to scheduling, this will help you get a jump start to understanding the mechanics and benefits of good scheduling practices; if you are a veteran of scheduling, you may discover a thing or two that will work better for you in bringing projects in on time.
This presentation will focus on the three simple questions that will help to keep projects on track and provides PM’s with the tools and confidence to embrace uncertainty: 1. 'What don't we know?' 2. 'What do we know?' 3. 'How can we fill the knowledge gap to get that information?'
Become a “PMO+” professional: complement your PMO skills with an approach to trigger more intrinsic motivation in program management
Today, there is plenty of program/project management methodology around (Waterfall, PRINCE2, Agile, …). They all have 1 thing in common (which is also their biggest shortcoming): it’s essentially a “hard” approach: a combination of structures, steps, controls, procedures, KPIs … to make people do what they should do in the program/project.