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.
46 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. As a result, it may be perceived that the key for project success is planning and that the most important skills for a project manager are planning skills. Is this really the case? In reality of high uncertainty is it possible that planning has a much lesser effect on performance than the common perception? Are the common planning practices enabling successful execution or promoting a self-fulfilling prophecy of failure? In this webinar we will discuss the effects of the common planning practices, the importance of execution and how to better balance the two so that the ultimate objective of successful project completion is better realized.
Most projects are not successful. According to a 2014 survey, less than 30% of capital projects are delivered on time or on budget. Planning and executing a successful project requires finding balance between the project schedule and risk.
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.
Too often, Project Managers are viewed (and view themselves) as administrators rather than leaders and significantly diminish the value that they can provide to the organization. By changing this perception we can deliver more value, build stronger teams, and create a more fulfilling workplace.
This webinar is designed for senior to advanced project leaders who are responsible for leading projects in a volatile, uncertain, complex, and ambiguous (VUCA) world.
This webinar discusses the second-in-command as a person of importance not impertinence. Examples from both classic literature, fictional characters that most of us recognize, and current events will be offered as forms of case studies. The second-in-command is very visible in project teams as a person that may want to help, but sometimes is not recognized by the project team lead or manager. Listen as Chris Greco explains the very nature of the second-in-command and how these "followers" are in fact not only necessary, but most often crucial to the success or failure of the team.
In the context of benefits management a comment was recently made that a benefit map was the most valuable tool, but is often misunderstood and/or misused. Benefits maps can be the most valuable tool in the benefits management toolkit which can provide a huge amount of value - if done correctly.