Back to School: Strategies and Resources for Student Engagement
New assets and resources created by academic outreach volunteers to help chapters engage with their universities, faculty members and students.
Page: 1 2 3 4 5 6 7 8 9 10 11......21 next>
New assets and resources created by academic outreach volunteers to help chapters engage with their universities, faculty members and students.
New assets and resources created by academic outreach volunteers to help chapters engage with their universities, faculty members and students.
New assets and resources created by academic outreach volunteers to help chapters engage with their universities, faculty members and students.
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.
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.
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.
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.
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.
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.
Page: 1 2 3 4 5 6 7 8 9 10 11......21 next>
"Get your facts first, and then you can distort them as much as you please." - Mark Twain |