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.
TOOLS TRAINING LIVE WEBINARS USER-GENERATED
|Deliverable Templates Project Plans Checklists Presentations|
|Language:||All English Arabic French Japanese Korean Portuguese Romanian Russian Spanish|
|Access:||All Free Premium|
|All A B C D E F G H I J K L M N O P Q R S T U V W X Y Z|
61 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.
This is the grandmother of all balanced scorecard templates! Here are 18 (count 'em, 18!) Excel templates that will help you develop a balanced score card from start to finish.
This is an example of a basic Project Charter, focusing on what is being done and who is responsible. Use this instructional document as an example of how to put a Project Charter together.
In a bid to embrace agile trends, organizations are rushing to implement agile practices rather than adopting an agile mindset. In this interactive session, Dr. Helen Uzamere will elucidate the difference between "Being Agile" and implementing agile practices, such as Scrum, XP, Kanban and demonstrate why an agile mindset, not practices, drives successful projects.
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.
One of the most difficult, yet important, questions regarding projects is "What advantages will this project create for the investors and key stakeholders?" Projects and programs should be treated as investments. This means that the focus of projects shifts from delivering within the triple constraints (time–cost–quality) towards some of the more fundamental questions: What is the purpose of this investment? What are the specific advantages expected? Are these benefits worth the investment?
This template aims to tie business case commitments to specific tracking activities and measures. Not all projects will have objective measures, but it is not acceptable to ignore that form of benefit realization for all initiatives. This plan should be completed at the same time as the business case, and the measured and total benefits identified here should align with the commitments made in the business case.