Rally - How to use it
•
1 like•1,593 views
A talk I gave internally at Wotif about using Rally, from RallyDev, for managing iterations. Generally good advice on how to run a team using Rally as a project-management tool (at least I think so)
Report
Share
Report
Share
Download to read offline
Recommended
Agile & Scrum Training
The document provides an agenda and overview of an introductory training on Agile and Scrum frameworks. It discusses key concepts like the Agile Manifesto, Scrum values and roles, and the differences between Scrum and traditional Waterfall methodologies. It also covers topics like product vision, role engagement, planning, estimation, and Scrum simulations.
Scrum 101
This presentation describes the basics of Agile methodologies and how it is differed from Waterfall. Then continues with the most famous Agile approach: Scrum
Agile Scrum Training, Day 1 (1/2)
Training materials for Agile Scrum. Starts with an overview of Agile and Lean. Followed with the Agile Scrum key concepts like Product Owner, Scrum Master, Scrum Team and Product Backlog. Theory is complemented with learnings and best practices from real life software development.
Agile Scrum Training Process
The document provides an overview of the Agile Scrum process. It describes traditional waterfall methodologies and how Agile and Scrum differ by being more iterative, collaborative with stakeholders, and able to adapt to changes. The Scrum framework involves three main roles - Product Owner, Scrum Master, and Team. It also describes the four main Scrum ceremonies - Sprint Planning Meeting, Daily Standup, Sprint Review, and Sprint Retrospective - as well as the typical artifacts like Product Backlog and Sprint Backlog.
Scrum In Ten Slides
When I needed to do presentations of Scrum to executives and students, I started to look for existing ones. Most presentations I found were very good for detailed presentations or training. But what I was looking for was a presentation I could give in less than 15 minutes (or more if I wanted). Most of them also contained out dated content. For example, the latest changes in the Scrum framework were not present and what has been removed was still there.
UPDATE VERSION : https://www.slideshare.net/pmengal/scrum-in-ten-slides-v20-2018
Agile
This document provides an overview of agile methodology and several agile frameworks. It begins with a brief history of the traditional waterfall model and its limitations. It then introduces the agile manifesto and some core agile principles. Several agile frameworks are described at a high level, including scrum, kanban, extreme programming, and others. Key practices of scrum and extreme programming like iterations, user stories, stand-up meetings, and test-driven development are defined. The document aims to give the reader a broad understanding of agile concepts and some of the most commonly used agile frameworks and practices.
Waterfall vs agile approach scrum framework and best practices in software d...
The document discusses various topics related to software development approaches, including:
1. The differences between waterfall and agile approaches. Agile focuses on iterative development and responding to change over extensive planning.
2. Common problems with traditional project management like late delivery and budget overruns.
3. An overview of the Scrum framework, including roles, artifacts, ceremonies, and best practices. Scrum uses short iterations called sprints to iteratively deliver working software.
4. Recommendations to customize Scrum by incorporating elements of eXtreme Programming (XP) and lean principles to eliminate waste and continually improve processes.
Scrum 101: Introduction to Scrum
This document provides an introduction to Scrum, an agile framework for project management. It discusses the principles of agile development and Scrum, including self-organizing cross-functional teams, short sprint cycles, daily stand-ups, product backlogs and user stories, estimation techniques, and retrospectives for continuous improvement. The Scrum framework emphasizes empiricism, adaptation, transparency, inspection, and frequent delivery of working software.
Recommended
Agile & Scrum Training
The document provides an agenda and overview of an introductory training on Agile and Scrum frameworks. It discusses key concepts like the Agile Manifesto, Scrum values and roles, and the differences between Scrum and traditional Waterfall methodologies. It also covers topics like product vision, role engagement, planning, estimation, and Scrum simulations.
Scrum 101
This presentation describes the basics of Agile methodologies and how it is differed from Waterfall. Then continues with the most famous Agile approach: Scrum
Agile Scrum Training, Day 1 (1/2)
Training materials for Agile Scrum. Starts with an overview of Agile and Lean. Followed with the Agile Scrum key concepts like Product Owner, Scrum Master, Scrum Team and Product Backlog. Theory is complemented with learnings and best practices from real life software development.
Agile Scrum Training Process
The document provides an overview of the Agile Scrum process. It describes traditional waterfall methodologies and how Agile and Scrum differ by being more iterative, collaborative with stakeholders, and able to adapt to changes. The Scrum framework involves three main roles - Product Owner, Scrum Master, and Team. It also describes the four main Scrum ceremonies - Sprint Planning Meeting, Daily Standup, Sprint Review, and Sprint Retrospective - as well as the typical artifacts like Product Backlog and Sprint Backlog.
Scrum In Ten Slides
When I needed to do presentations of Scrum to executives and students, I started to look for existing ones. Most presentations I found were very good for detailed presentations or training. But what I was looking for was a presentation I could give in less than 15 minutes (or more if I wanted). Most of them also contained out dated content. For example, the latest changes in the Scrum framework were not present and what has been removed was still there.
UPDATE VERSION : https://www.slideshare.net/pmengal/scrum-in-ten-slides-v20-2018
Agile
This document provides an overview of agile methodology and several agile frameworks. It begins with a brief history of the traditional waterfall model and its limitations. It then introduces the agile manifesto and some core agile principles. Several agile frameworks are described at a high level, including scrum, kanban, extreme programming, and others. Key practices of scrum and extreme programming like iterations, user stories, stand-up meetings, and test-driven development are defined. The document aims to give the reader a broad understanding of agile concepts and some of the most commonly used agile frameworks and practices.
Waterfall vs agile approach scrum framework and best practices in software d...
The document discusses various topics related to software development approaches, including:
1. The differences between waterfall and agile approaches. Agile focuses on iterative development and responding to change over extensive planning.
2. Common problems with traditional project management like late delivery and budget overruns.
3. An overview of the Scrum framework, including roles, artifacts, ceremonies, and best practices. Scrum uses short iterations called sprints to iteratively deliver working software.
4. Recommendations to customize Scrum by incorporating elements of eXtreme Programming (XP) and lean principles to eliminate waste and continually improve processes.
Scrum 101: Introduction to Scrum
This document provides an introduction to Scrum, an agile framework for project management. It discusses the principles of agile development and Scrum, including self-organizing cross-functional teams, short sprint cycles, daily stand-ups, product backlogs and user stories, estimation techniques, and retrospectives for continuous improvement. The Scrum framework emphasizes empiricism, adaptation, transparency, inspection, and frequent delivery of working software.
Scrum
Scrum is an agile framework for managing software delivery that uses iterative sprints to frequently deliver working software. Sprints are short, timed iterations where teams select backlog items to complete. There are ceremonies like sprint planning, daily scrums, sprint reviews, and retrospectives. Roles include the product owner who manages requirements and priorities, the scrum master who removes impediments, and the cross-functional scrum team which self-organizes to deliver working software every sprint.
Scrum
Scrum is an agile framework for managing product development. It defines three roles - Scrum Master, Product Owner, and Development Team - and three artifacts - Product Backlog, Sprint Backlog, and Product Increment. It also includes five ceremonies - Product Backlog Refinement, Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective. Scrum was first defined in 1986 and evolved through the 1990s, with Ken Schwaber and Jeff Sutherland formalizing the method in 2001 in their book Agile Software Development with Scrum.
Agile Fundamentals
A short talk that explains a little of what Agile is; where it originated and how it works. This talk is applicable whatever method you use - scrum, XP, DSDM etc. Concludes by introducing ICAgile (the International Consortium of Agile).
Scrum
The document provides an overview of Scrum, including its values, principles, roles, meetings, artifacts, and processes. The four values of the Agile Manifesto are listed, followed by the twelve principles. Scrum roles include the Product Owner, Scrum Master, and Development Team. Key Scrum events include the Backlog Refinement, Sprint Planning, Daily Scrum, Sprint Review, and Retrospective meetings. Main artifacts are the Product Backlog, Sprint Backlog, and Sprint Burn Down Chart.
Agile presentation
The document provides an agenda for a JIRA Agile workshop. It begins with an overview of Agile and Scrum principles and frameworks. It then discusses what JIRA is and some of its key concepts like issues, projects, tasks, and stories. The document outlines JIRA features, workflows, user management, and tools like reports, boards, dashboards, and time tracking. It distinguishes between story point and effort estimation. Finally, it leaves time for questions.
Agile Methodology
The document provides an overview of agile methodology and scrum framework. It begins with a short history of traditional waterfall software development processes and their limitations. It then introduces the agile manifesto and values, as well as the 12 agile principles. A key part of agile is iterative development with short sprints. Scrum is discussed as one of the major agile frameworks, outlining its ceremonies like sprint planning, daily standups, and retrospectives. Scrum roles of product owner, scrum master, and self-organizing team are also summarized.
Synerzip Agile Cheat Sheet
The document provides an overview of Agile concepts including roles, artifacts, meetings, and practices. It describes Scrum roles like the Scrum Team, Product Owner, and Scrum Master. It outlines artifacts like the Product Backlog, Sprint Backlog, and Burndown Chart. It explains meetings in Scrum like Sprint Planning, Daily Scrum, Sprint Review, and Retrospective. Finally, it touches on practices like estimating with story points, assigning business value, and tracking velocity.
Introduction to Scrum.ppt
The document provides an overview of the waterfall model and agile methodologies for software development projects. It discusses:
- The linear sequential phases of the waterfall model and when it is suitable.
- Issues with the waterfall model like inability to handle changes and lack of testing throughout.
- Benefits of agile like ability to adapt to changes, early delivery of working software, and improved success rates.
- Key aspects of the Scrum agile framework like sprints, daily stand-ups, and product backlogs.
- Differences in how development costs are treated as capital expenditures or operating expenses between waterfall, agile, and cloud-based models.
Jira Training
The document provides an overview of JIRA concepts including projects, issues, statuses, resolutions, and priorities. A project contains a collection of issues and has a name and key. Issues represent bugs, epics, improvements, features, stories, and tasks. Statuses track an issue's stage from open to in progress, resolved, and closed. Resolutions indicate how an issue was addressed like fixed, won't fix, or duplicate. Priorities denote an issue's importance from blocker to critical, major, minor, and trivial.
Agile boards in Jira Are For Everyone
Sometimes one board per project just isn't enough! Why should development teams get all the fun?! This presentation explores how teams can use Kanban and Scrum boards for any part of your development cycle - from idea to deployment and beyond!
Agile Introduction - Scrum Framework
This document provides an overview of Agile methodology and Scrum framework. It defines key Agile concepts like iterations called sprints and artifacts like product backlog, sprint backlog, and product increment. It describes Scrum roles of product owner, Scrum master, and team. It outlines Scrum activities like sprint planning, daily scrum, sprint review, and retrospective. Finally, it discusses tools like task boards and burn down charts used to provide transparency and track progress.
Agile best practices
The document discusses various best practices used in Agile project management. Some key Agile practices mentioned include iterations, customer-oriented approach, product backlog, user stories, Scrum meetings, and automated testing. It provides details on how each practice works and its benefits. For example, it notes that iterations allow teams to select work based on available hours, while product backlogs help prioritize and detail customer requirements to guide development work.
Agile (Scrum)
The document provides an overview of Agile methodology and Scrum framework. It describes that Agile is an alternative project management approach that uses short iterative cycles called sprints to incrementally deliver working software. Scrum is the most commonly used Agile framework and involves roles of Product Owner, Scrum Master, and team. It uses artifacts like Product Backlog and Sprint Backlog and events like Sprint Planning, Daily Scrum, and Sprint Review.
Scrum
The document contains a series of links to images without any connecting text. The images appear to be related to agile software development practices and include depictions of sprints, backlogs, planning poker, burndowns, retrospectives and other agile concepts.
Scrum Guide In One Slide
Scrum is an agile framework that focuses on transparency, inspection, and adaptation through sprints, daily scrums, sprint reviews, and retrospectives. Key roles include the Product Owner who manages priorities, the Development Team who does the work, and the Scrum Master who facilitates the process. Events and artifacts like the product and sprint backlogs help ensure transparency and progress toward completing an increment of work each sprint based on a shared definition of done.
Apt agile methodology
The document provides an overview of the Agile methodology, including its history, principles, characteristics, and popular methods like Scrum and Extreme Programming (XP). It describes how Agile evolved in the 1990s as an alternative to heavyweight methods like the Waterfall model. Key aspects of Agile include iterative development, frequent delivery of working software, collaboration between self-organizing cross-functional teams, and responding to change over following a plan.
Agile ceremonies
The document discusses several agile ceremonies that originate from scrum methodology, including sprint planning, backlog grooming, daily stand-ups, iteration reviews, and retrospectives. It provides details on the purpose and structure of each ceremony, such as typical attendees, duration, and topics covered. The ceremonies are presented as regular meetings that facilitate communication within agile teams and help ensure continuous improvement.
Agile Process Introduction
This document provides an overview of different software development processes including the waterfall model, iterative model, Rational Unified Process (RUP), and Agile Development Process (ADP). It describes the key aspects of each process including phases, roles, artifacts, and ceremonies. Specifically, it provides detailed explanations of Scrum, an agile methodology, including Scrum roles like Product Owner and Scrum Master, ceremonies like the Daily Scrum, and artifacts like the Product Backlog and Sprint Backlog. The document concludes with references for further information.
Overview of agile
The document provides an overview of Agile methodology. It begins with a brief history of the waterfall software development process and its limitations. It then discusses the Agile Manifesto and its core values that favor individuals, collaboration, responding to change, and working software over processes, tools, contracts and plans. Specific Agile frameworks like Scrum and Kanban are then outlined, with Scrum focusing on sprints, daily stand-ups, and no changes during a sprint, while Kanban emphasizes visualizing and limiting work in progress and managing lead times. The document aims to explain the key concepts and differences of Agile approaches.
Agile Project and Portfolio Management Using Jira - AgileSolutions
A deck I've used to provide Agile Project Management training based on Scrum using a set of issues imported to create a website development project
Next Level Agile - Ryan Polk
The next level of agile will take you through how agile at scale is different then the team level agile. Strong agile basics are always key to a successful business and why connecting delivery to strategy is essential in realizing the promise of agile. This will help you understand where you are in your agile journey, how to identify trouble spots, and how to fix them.
Benefits of Test Management Tool - Rally
The document discusses the benefits of using Rally, an agile test management tool, in software development and testing projects. It notes that agile development is becoming the norm. Rally helps manage requirements, estimation, test case creation, execution, defect tracking, and reporting throughout the agile project lifecycle. It integrates with other tools and provides benefits like real-time status, coordination across teams, and analytics. An example case study describes how Rally was used effectively over multiple sprints in one of Marlabs' client projects to plan, track progress, link defects to user stories, and generate reports.
More Related Content
What's hot
Scrum
Scrum is an agile framework for managing software delivery that uses iterative sprints to frequently deliver working software. Sprints are short, timed iterations where teams select backlog items to complete. There are ceremonies like sprint planning, daily scrums, sprint reviews, and retrospectives. Roles include the product owner who manages requirements and priorities, the scrum master who removes impediments, and the cross-functional scrum team which self-organizes to deliver working software every sprint.
Scrum
Scrum is an agile framework for managing product development. It defines three roles - Scrum Master, Product Owner, and Development Team - and three artifacts - Product Backlog, Sprint Backlog, and Product Increment. It also includes five ceremonies - Product Backlog Refinement, Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective. Scrum was first defined in 1986 and evolved through the 1990s, with Ken Schwaber and Jeff Sutherland formalizing the method in 2001 in their book Agile Software Development with Scrum.
Agile Fundamentals
A short talk that explains a little of what Agile is; where it originated and how it works. This talk is applicable whatever method you use - scrum, XP, DSDM etc. Concludes by introducing ICAgile (the International Consortium of Agile).
Scrum
The document provides an overview of Scrum, including its values, principles, roles, meetings, artifacts, and processes. The four values of the Agile Manifesto are listed, followed by the twelve principles. Scrum roles include the Product Owner, Scrum Master, and Development Team. Key Scrum events include the Backlog Refinement, Sprint Planning, Daily Scrum, Sprint Review, and Retrospective meetings. Main artifacts are the Product Backlog, Sprint Backlog, and Sprint Burn Down Chart.
Agile presentation
The document provides an agenda for a JIRA Agile workshop. It begins with an overview of Agile and Scrum principles and frameworks. It then discusses what JIRA is and some of its key concepts like issues, projects, tasks, and stories. The document outlines JIRA features, workflows, user management, and tools like reports, boards, dashboards, and time tracking. It distinguishes between story point and effort estimation. Finally, it leaves time for questions.
Agile Methodology
The document provides an overview of agile methodology and scrum framework. It begins with a short history of traditional waterfall software development processes and their limitations. It then introduces the agile manifesto and values, as well as the 12 agile principles. A key part of agile is iterative development with short sprints. Scrum is discussed as one of the major agile frameworks, outlining its ceremonies like sprint planning, daily standups, and retrospectives. Scrum roles of product owner, scrum master, and self-organizing team are also summarized.
Synerzip Agile Cheat Sheet
The document provides an overview of Agile concepts including roles, artifacts, meetings, and practices. It describes Scrum roles like the Scrum Team, Product Owner, and Scrum Master. It outlines artifacts like the Product Backlog, Sprint Backlog, and Burndown Chart. It explains meetings in Scrum like Sprint Planning, Daily Scrum, Sprint Review, and Retrospective. Finally, it touches on practices like estimating with story points, assigning business value, and tracking velocity.
Introduction to Scrum.ppt
The document provides an overview of the waterfall model and agile methodologies for software development projects. It discusses:
- The linear sequential phases of the waterfall model and when it is suitable.
- Issues with the waterfall model like inability to handle changes and lack of testing throughout.
- Benefits of agile like ability to adapt to changes, early delivery of working software, and improved success rates.
- Key aspects of the Scrum agile framework like sprints, daily stand-ups, and product backlogs.
- Differences in how development costs are treated as capital expenditures or operating expenses between waterfall, agile, and cloud-based models.
Jira Training
The document provides an overview of JIRA concepts including projects, issues, statuses, resolutions, and priorities. A project contains a collection of issues and has a name and key. Issues represent bugs, epics, improvements, features, stories, and tasks. Statuses track an issue's stage from open to in progress, resolved, and closed. Resolutions indicate how an issue was addressed like fixed, won't fix, or duplicate. Priorities denote an issue's importance from blocker to critical, major, minor, and trivial.
Agile boards in Jira Are For Everyone
Sometimes one board per project just isn't enough! Why should development teams get all the fun?! This presentation explores how teams can use Kanban and Scrum boards for any part of your development cycle - from idea to deployment and beyond!
Agile Introduction - Scrum Framework
This document provides an overview of Agile methodology and Scrum framework. It defines key Agile concepts like iterations called sprints and artifacts like product backlog, sprint backlog, and product increment. It describes Scrum roles of product owner, Scrum master, and team. It outlines Scrum activities like sprint planning, daily scrum, sprint review, and retrospective. Finally, it discusses tools like task boards and burn down charts used to provide transparency and track progress.
Agile best practices
The document discusses various best practices used in Agile project management. Some key Agile practices mentioned include iterations, customer-oriented approach, product backlog, user stories, Scrum meetings, and automated testing. It provides details on how each practice works and its benefits. For example, it notes that iterations allow teams to select work based on available hours, while product backlogs help prioritize and detail customer requirements to guide development work.
Agile (Scrum)
The document provides an overview of Agile methodology and Scrum framework. It describes that Agile is an alternative project management approach that uses short iterative cycles called sprints to incrementally deliver working software. Scrum is the most commonly used Agile framework and involves roles of Product Owner, Scrum Master, and team. It uses artifacts like Product Backlog and Sprint Backlog and events like Sprint Planning, Daily Scrum, and Sprint Review.
Scrum
The document contains a series of links to images without any connecting text. The images appear to be related to agile software development practices and include depictions of sprints, backlogs, planning poker, burndowns, retrospectives and other agile concepts.
Scrum Guide In One Slide
Scrum is an agile framework that focuses on transparency, inspection, and adaptation through sprints, daily scrums, sprint reviews, and retrospectives. Key roles include the Product Owner who manages priorities, the Development Team who does the work, and the Scrum Master who facilitates the process. Events and artifacts like the product and sprint backlogs help ensure transparency and progress toward completing an increment of work each sprint based on a shared definition of done.
Apt agile methodology
The document provides an overview of the Agile methodology, including its history, principles, characteristics, and popular methods like Scrum and Extreme Programming (XP). It describes how Agile evolved in the 1990s as an alternative to heavyweight methods like the Waterfall model. Key aspects of Agile include iterative development, frequent delivery of working software, collaboration between self-organizing cross-functional teams, and responding to change over following a plan.
Agile ceremonies
The document discusses several agile ceremonies that originate from scrum methodology, including sprint planning, backlog grooming, daily stand-ups, iteration reviews, and retrospectives. It provides details on the purpose and structure of each ceremony, such as typical attendees, duration, and topics covered. The ceremonies are presented as regular meetings that facilitate communication within agile teams and help ensure continuous improvement.
Agile Process Introduction
This document provides an overview of different software development processes including the waterfall model, iterative model, Rational Unified Process (RUP), and Agile Development Process (ADP). It describes the key aspects of each process including phases, roles, artifacts, and ceremonies. Specifically, it provides detailed explanations of Scrum, an agile methodology, including Scrum roles like Product Owner and Scrum Master, ceremonies like the Daily Scrum, and artifacts like the Product Backlog and Sprint Backlog. The document concludes with references for further information.
Overview of agile
The document provides an overview of Agile methodology. It begins with a brief history of the waterfall software development process and its limitations. It then discusses the Agile Manifesto and its core values that favor individuals, collaboration, responding to change, and working software over processes, tools, contracts and plans. Specific Agile frameworks like Scrum and Kanban are then outlined, with Scrum focusing on sprints, daily stand-ups, and no changes during a sprint, while Kanban emphasizes visualizing and limiting work in progress and managing lead times. The document aims to explain the key concepts and differences of Agile approaches.
Agile Project and Portfolio Management Using Jira - AgileSolutions
A deck I've used to provide Agile Project Management training based on Scrum using a set of issues imported to create a website development project
What's hot (20)
Agile Project and Portfolio Management Using Jira - AgileSolutions
Agile Project and Portfolio Management Using Jira - AgileSolutions
Viewers also liked
Next Level Agile - Ryan Polk
The next level of agile will take you through how agile at scale is different then the team level agile. Strong agile basics are always key to a successful business and why connecting delivery to strategy is essential in realizing the promise of agile. This will help you understand where you are in your agile journey, how to identify trouble spots, and how to fix them.
Benefits of Test Management Tool - Rally
The document discusses the benefits of using Rally, an agile test management tool, in software development and testing projects. It notes that agile development is becoming the norm. Rally helps manage requirements, estimation, test case creation, execution, defect tracking, and reporting throughout the agile project lifecycle. It integrates with other tools and provides benefits like real-time status, coordination across teams, and analytics. An example case study describes how Rally was used effectively over multiple sprints in one of Marlabs' client projects to plan, track progress, link defects to user stories, and generate reports.
Rally For Impact Introduction
Empathetic entrepreneurs are business owners who care about social and environmental issues. They use their companies to make a positive difference in addition to earning a profit. Examples include companies focused on renewable energy, fair trade, and providing access to healthcare and education in developing countries.
Adopting A Whole Team Approach To Quality
A presentation give at Agile Carolinas on some things that I think are needed to build quality software.
The content of the presentation is in the presenter notes.
Unlocking Excellence with Agile Metrics
Learn about the importance of measuring the right things and how to use metrics and data to improve performance. Get the right metrics and KPIs to improve performance so you can deliver on your organization’s most important initiatives.
Read The Seven Deadly Sins of Agile Measurement http://2ral.ly/Zqa to make sure you’re measuring performance in a way that actually improves results.
The A3 Agile Business: An Agile Alignment Approach
As scale and distribution set in at organisations that have strong growth, spreading the lean and agile culture becomes even more important to keep teams aligned and motivated. At Rally, we have fallen in love with A3 Thinking and templates to address this challenge. We do new hire bootcamps, employee trainings and walk the talk, but A3’s seem to be the most effective tool for helping us spread lean thinking and empower teams to share their problems and strategies. This talk will tell our story, challenge the audience and provide some education on these powerful tools for enabling teams to collaborate, steer and take action.
Introduction to (hill) rally navigation
The document provides guidance for navigators in hill rallies, outlining their primary tasks of managing paperwork, navigating between time controls using a road book, and keeping the driver on schedule. It explains key rally terms like time controls, target times, and time cards that navigators must understand to properly do their job. The time schedule example shows the scheduled times, target times, and penalties for lateness across stages and services for the first leg of a sample rally.
Executive Experience Reports
Executives at large companies are adopting Agile practices to address issues like being late to market with features, slow ability to change, and declining stock prices. They use Rally's Agile tools and coaching to help transform their organizations, seeing benefits like quicker delivery of high-quality releases, improved prioritization to focus on the most important work, and increased productivity and visibility across distributed teams. The document advocates that other large companies seeking business transformation should partner with Rally to implement Agile at scale and hear from peer executives on their experiences.
Why Agile?
The document provides an overview of Agile development and how to get started with an Agile approach. It discusses some of the benefits of Agile such as increased productivity, quality and stakeholder satisfaction compared to traditional waterfall approaches. It also addresses common objections to Agile. The document then describes key aspects of implementing Agile including Scrum roles and processes and tips for getting teams trained in Agile.
Benefits Of Implementing Test Management Tools
Testing is the procedure of exercising software in order to check whether it is capable of satisfying certain requirements and to detect errors. The key objectives of software testing is to recognize detects, non-conformance and other allied threats in a work product in order to communicate all known concerns to the project group and make sure that every issue is addressed in an apt manner prior to release.
When Worlds Collide by Karl Scotland
The right management approach will always differ between
companies. lean has recently been breaking down barriers
in its application to a range of industries stemming from its
strong manufacturing background. But how does it compete
against similar, yet slightly different management practices
such as agile? and more so, can the two happily co-exist?
agile coach karl scotland, explains how cloud-based
solutions provider, Rally Software, used both lean and agile practices
together to best meet its customer’s needs.
Rally at AT&T - Sigal Pasternak - Agile Israel 2013
AT&T Israel implemented the Rally project management tool across 47 Scrum teams and 500 employees across 4 business units. Rally provided visibility into transforming business requirements into delivered projects and releases. The implementation started with two lines of business in 2011 and expanded to full use across all teams by December 2011. Rally provided practices alignment, a standard view of projects, and visibility for managers.
CA Agile Central (formerly Rally) Inside DevOps
So you just got CA Agile Central. Now what? How does this fit into your organization’s development workflow and delivery pipeline? Come hear about how CA Agile Central provides transparency into your engineering organization.
For more information, please visit http://cainc.to/Nv2VOe
Using JIRA & Greenhopper for Agile Development
This document discusses using JIRA and Greenhopper for agile development. It provides an overview of JIRA as an issue tracking platform that can be used for various purposes including project management, help desk support, and software development. It also discusses Greenhopper, an agile project management plugin for JIRA that includes planning, task, and chart boards. The document concludes by encouraging evaluation of JIRA and Greenhopper.
Viewers also liked (14)
The A3 Agile Business: An Agile Alignment Approach
The A3 Agile Business: An Agile Alignment Approach
Rally at AT&T - Sigal Pasternak - Agile Israel 2013
Rally at AT&T - Sigal Pasternak - Agile Israel 2013
Similar to Rally - How to use it
Kanban vs Scrum: What's the difference, and which should you use?
Originally presented at the 207 Lean Transformation Conference, this presentation provides a practical introduction to Scrum, particularly for public sector employees, and guides you to deciding whether Kanban or Scrum will work best for your teams and projects.
Estimating time-tracking
This document discusses the importance of estimating and tracking time for documentation projects. It recommends tracking all time spent on tasks like meetings, writing, editing, and more to build a basis for accurate estimating. Both bottom-up and top-down estimating methods are described. Tracking time allows learning from past projects to improve estimates using techniques like comparative, parametric, and matrix-based estimating. Correlating estimates with tracking provides feedback to refine estimates. Risks should be identified and stakeholders agree on estimates upfront to manage scope changes.
Sdec11.agile ina day
The document provides instructions for an Agile in a Day workshop. Participants are instructed to sit with others who have different levels of Agile experience. They then initial questions they want to learn and discuss challenges to adopting Agile. The workshop covers Agile concepts through activities like visioning, user stories, mapping stories and estimating. Participants work through an iteration, including planning, a standup and retrospective. They conclude by reviewing what they learned.
Introduction to agile and Scrum
Introduction to agile and Scrum.
Using Vera Peeters and Pascal Van Cauwenberghe's XP game as a basis, we have adapted it to explain and demonstrate agile and Scrum. The second half of the presentation is largely repetitive because it is used at each stage in the game.
What is scrum
This document provides an overview of Agile and Scrum concepts and processes. It describes the purpose of Scrum as delivering value through incremental releases. The key roles of Product Owner, Scrum Master, and Team are outlined. Scrum artifacts like the Product and Sprint Backlogs and their purposes are defined. Meeting ceremonies like Sprint Planning, Daily Scrum, Review and Retrospective are summarized along with their goals and timing. The document emphasizes continuous inspection and adaptation through its cadenced processes.
Agile projetcs (sizing and estimation)
Unlike traditional projects, Agile teams provide their estimates using a “top-down” approach; where they use current available information to produce gross-level estimation, and this estimation is less accurate and has less details.
============== Follow us ==============
Website: http://xpdays.org
Linked In: https://www.linkedin.com/company/xpdays
Facebook: https://www.facebook.com/xpdaysorg
Twitter: https://twitter.com/xpdaysorg
Va overload-presentation- final
The document discusses how to avoid overwhelm as a virtual assistant by providing tips for good project management habits including managing email, calendars and tasks, as well as a three step approach to staying organized, it also emphasizes the importance of using a project management system to plan, organize and manage projects in order to be successful.
Xanpan extended presentation
Xanpan is a hybrid agile methodology that combines elements of Kanban and Extreme Programming (XP). It is described as team-centric and emphasizes continuous flow, small batch sizes, visualizing work, and quality. Some key practices include using XP technical practices like test-driven development, breaking stories into tasks, estimating in story points, applying work-in-progress limits, and having regular iteration cycles with deadlines. The methodology aims to take the best of Kanban and XP while allowing teams flexibility in customizing their process.
Agile Scrum Estimation
The document discusses different approaches to estimation in waterfall and Scrum methodologies. In Scrum, teams estimate their own work in story points, which are relative units based on size and complexity. Story points help drive cross-functional behavior and do not decay over time. Ideal days estimates involve determining how long a task would take with ideal conditions and no interruptions. Planning poker uses story point cards to facilitate discussion and reach consensus on estimates. Release planning in Scrum involves estimating velocity over sprints to determine how many product backlog items can be completed.
Jeff Lopez - To Affinity and Beyond
The document describes a workshop that demonstrates affinity mapping techniques for agile planning. It will show how to quickly generate, estimate, prioritize and evaluate a product backlog through affinity consensus. Attendees will learn techniques like dot voting, grouping and relative sizing. Exercises will guide participants in creating user stories, estimating effort and determining value through affinity facilitation. The goal is to reduce waste and allow for fast decision making through these visual and collaborative techniques.
Jeff Lopez - To Affinity and Beyond
Jeff Lopez Presentation for Agile Impact Conference 2018 Day 1.
"Learn speedy affinity facilitation techniques to eliminate waste and boost productivity in creating, prioritizing and estimating a backlog."
Introduction to Agile - Scrum, Kanban, and everything in between
This document provides an introduction to Agile project management frameworks like Scrum and Kanban. It discusses the limitations of traditional waterfall project management and how Agile aims to address these issues through iterative development, collaboration, and flexibility. Key aspects of Scrum like roles, events, artifacts, estimation and user stories are explained. Kanban concepts such as visualizing workflow, limiting work in progress, and managing flow are also covered. The document recommends resources for learning more about Agile, Scrum, Kanban and hybrid approaches.
Estimation Protips - NCDevCon 2014
Estimates are not promises
Your gut lies
Premature estimation is sabotage
Big teams are slower than small ones
Beware unwarranted precision
Count all the things!
When in a pinch, use a proxy
You can’t negotiate math
Incorporating UX into an Agile Methodology
The document discusses incorporating user experience (UX) design into an Agile development methodology. It outlines the key parts of Agile like user stories, backlogs, and sprints. It then provides three principles for combining UX and Agile: iterate by making mistakes faster, scale by doing more with less, and simplify by keeping things "good enough." Specific tactics are described like using Sprint Zero to get ahead, prioritizing work, and embracing failures to find solutions. The importance of the UX designer's mindset and role on an Agile team is emphasized.
Initial sprint velocity problem
This document discusses challenges with estimating velocity for the initial sprint of a new Scrum team. It notes that using past data from other teams is not accurate for a new team. While management wants estimates upfront, the best approach is to wait for real data from the first sprint. The document recommends a risk mitigation approach of estimating tasks in hours to approximate a velocity range for the first sprint. Additional challenges can arise from delivering a minimum viable product that does not match architectural needs.
Al Nelson on Project Management for Game Developers
This document discusses three project management methods - Kanban, Scrum, and Triage. Kanban uses a task board and daily stand-ups to continuously load balance work. Scrum uses fixed sprint cycles and stand-ups to solve problems. Triage uses a dashboard with countdowns and daily meetings to prioritize bugs and hit dates. The document provides overviews and "how-tos" for each, along with their strengths, weaknesses, and best uses. It also shows examples of tools used in each method and measures for success.
Intro to Agile Processes for Developers
Agile processes -- particularly SCRUM and Kanban -- are the best proven way to deliver high-quality software on-time and on-budget. Here are some basics to get started in bringing Agile to your organization!
Adamson "Blueprint for Managing Your Project"
This presentation was provided by Maureen Adamson of Adamson & Associates, during the NISO event "Project Management for the Information Community: Managing and Communicating the Process, Session Four," held on Friday, March 15, 2019.
NoEstimates@iNatuix
This document discusses the NoEstimates approach to software development. It begins by defining estimates and explaining that NoEstimates is about minimizing estimates rather than eliminating them entirely. The main goals of NoEstimates are to evaluate progress in a concrete way and force teams to slice work into smaller stories. Key benefits include being faster, easier iteration planning, and minimal time spent estimating. Progress is measured by the number of "Running Tested Stories" completed. The document also covers challenges, case studies, and debates around using NoEstimates versus more traditional estimating approaches.
Estimation Protips
You’re an expert developer, peacefully composing code into a profoundly elegant masterpiece, when suddenly your boss rushes in with the Next Big Idea that will Revolutionize The Way People Use The Internet. He’s on his way to pitch to a VC, and stops by to describe the Idea in excited terms. After a 30 second elevator pitch, he pops the question: “So, Peter, how long do you think it will take to build this thing-a-ma-bob?”
What do you say?
These eight Protips will cover your back, save your job, and keep your boss’s shirt.
Similar to Rally - How to use it (20)
Kanban vs Scrum: What's the difference, and which should you use?
Kanban vs Scrum: What's the difference, and which should you use?
Introduction to Agile - Scrum, Kanban, and everything in between
Introduction to Agile - Scrum, Kanban, and everything in between
Al Nelson on Project Management for Game Developers
Al Nelson on Project Management for Game Developers
Recently uploaded
Monitoring and Managing Anomaly Detection on OpenShift.pdf
Monitoring and Managing Anomaly Detection on OpenShift
Overview
Dive into the world of anomaly detection on edge devices with our comprehensive hands-on tutorial. This SlideShare presentation will guide you through the entire process, from data collection and model training to edge deployment and real-time monitoring. Perfect for those looking to implement robust anomaly detection systems on resource-constrained IoT/edge devices.
Key Topics Covered
1. Introduction to Anomaly Detection
- Understand the fundamentals of anomaly detection and its importance in identifying unusual behavior or failures in systems.
2. Understanding Edge (IoT)
- Learn about edge computing and IoT, and how they enable real-time data processing and decision-making at the source.
3. What is ArgoCD?
- Discover ArgoCD, a declarative, GitOps continuous delivery tool for Kubernetes, and its role in deploying applications on edge devices.
4. Deployment Using ArgoCD for Edge Devices
- Step-by-step guide on deploying anomaly detection models on edge devices using ArgoCD.
5. Introduction to Apache Kafka and S3
- Explore Apache Kafka for real-time data streaming and Amazon S3 for scalable storage solutions.
6. Viewing Kafka Messages in the Data Lake
- Learn how to view and analyze Kafka messages stored in a data lake for better insights.
7. What is Prometheus?
- Get to know Prometheus, an open-source monitoring and alerting toolkit, and its application in monitoring edge devices.
8. Monitoring Application Metrics with Prometheus
- Detailed instructions on setting up Prometheus to monitor the performance and health of your anomaly detection system.
9. What is Camel K?
- Introduction to Camel K, a lightweight integration framework built on Apache Camel, designed for Kubernetes.
10. Configuring Camel K Integrations for Data Pipelines
- Learn how to configure Camel K for seamless data pipeline integrations in your anomaly detection workflow.
11. What is a Jupyter Notebook?
- Overview of Jupyter Notebooks, an open-source web application for creating and sharing documents with live code, equations, visualizations, and narrative text.
12. Jupyter Notebooks with Code Examples
- Hands-on examples and code snippets in Jupyter Notebooks to help you implement and test anomaly detection models.
Best 20 SEO Techniques To Improve Website Visibility In SERP
Boost your website's visibility with proven SEO techniques! Our latest blog dives into essential strategies to enhance your online presence, increase traffic, and rank higher on search engines. From keyword optimization to quality content creation, learn how to make your site stand out in the crowded digital landscape. Discover actionable tips and expert insights to elevate your SEO game.
Presentation of the OECD Artificial Intelligence Review of Germany
Consult the full report at https://www.oecd.org/digital/oecd-artificial-intelligence-review-of-germany-609808d6-en.htm
Energy Efficient Video Encoding for Cloud and Edge Computing Instances
Energy Efficient Video Encoding for Cloud and Edge Computing Instances
Letter and Document Automation for Bonterra Impact Management (fka Social Sol...
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on automated letter generation for Bonterra Impact Management using Google Workspace or Microsoft 365.
Interested in deploying letter generation automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
dbms calicut university B. sc Cs 4th sem.pdf
Its a seminar ppt on database management system using sql
Introduction of Cybersecurity with OSS at Code Europe 2024
I develop the Ruby programming language, RubyGems, and Bundler, which are package managers for Ruby. Today, I will introduce how to enhance the security of your application using open-source software (OSS) examples from Ruby and RubyGems.
The first topic is CVE (Common Vulnerabilities and Exposures). I have published CVEs many times. But what exactly is a CVE? I'll provide a basic understanding of CVEs and explain how to detect and handle vulnerabilities in OSS.
Next, let's discuss package managers. Package managers play a critical role in the OSS ecosystem. I'll explain how to manage library dependencies in your application.
I'll share insights into how the Ruby and RubyGems core team works to keep our ecosystem safe. By the end of this talk, you'll have a better understanding of how to safeguard your code.
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
Discover the seamless integration of RPA (Robotic Process Automation), COMPOSER, and APM with AWS IDP enhanced with Slack notifications. Explore how these technologies converge to streamline workflows, optimize performance, and ensure secure access, all while leveraging the power of AWS IDP and real-time communication via Slack notifications.
Building Production Ready Search Pipelines with Spark and Milvus
Spark is the widely used ETL tool for processing, indexing and ingesting data to serving stack for search. Milvus is the production-ready open-source vector database. In this talk we will show how to use Spark to process unstructured data to extract vector representations, and push the vectors to Milvus vector database for search serving.
June Patch Tuesday
Ivanti’s Patch Tuesday breakdown goes beyond patching your applications and brings you the intelligence and guidance needed to prioritize where to focus your attention first. Catch early analysis on our Ivanti blog, then join industry expert Chris Goettl for the Patch Tuesday Webinar Event. There we’ll do a deep dive into each of the bulletins and give guidance on the risks associated with the newly-identified vulnerabilities.
GraphRAG for Life Science to increase LLM accuracy
GraphRAG for life science domain, where you retriever information from biomedical knowledge graphs using LLMs to increase the accuracy and performance of generated answers
Operating System Used by Users in day-to-day life.pptx
Dive into the realm of operating systems (OS) with Pravash Chandra Das, a seasoned Digital Forensic Analyst, as your guide. 🚀 This comprehensive presentation illuminates the core concepts, types, and evolution of OS, essential for understanding modern computing landscapes.
Beginning with the foundational definition, Das clarifies the pivotal role of OS as system software orchestrating hardware resources, software applications, and user interactions. Through succinct descriptions, he delineates the diverse types of OS, from single-user, single-task environments like early MS-DOS iterations, to multi-user, multi-tasking systems exemplified by modern Linux distributions.
Crucial components like the kernel and shell are dissected, highlighting their indispensable functions in resource management and user interface interaction. Das elucidates how the kernel acts as the central nervous system, orchestrating process scheduling, memory allocation, and device management. Meanwhile, the shell serves as the gateway for user commands, bridging the gap between human input and machine execution. 💻
The narrative then shifts to a captivating exploration of prominent desktop OSs, Windows, macOS, and Linux. Windows, with its globally ubiquitous presence and user-friendly interface, emerges as a cornerstone in personal computing history. macOS, lauded for its sleek design and seamless integration with Apple's ecosystem, stands as a beacon of stability and creativity. Linux, an open-source marvel, offers unparalleled flexibility and security, revolutionizing the computing landscape. 🖥️
Moving to the realm of mobile devices, Das unravels the dominance of Android and iOS. Android's open-source ethos fosters a vibrant ecosystem of customization and innovation, while iOS boasts a seamless user experience and robust security infrastructure. Meanwhile, discontinued platforms like Symbian and Palm OS evoke nostalgia for their pioneering roles in the smartphone revolution.
The journey concludes with a reflection on the ever-evolving landscape of OS, underscored by the emergence of real-time operating systems (RTOS) and the persistent quest for innovation and efficiency. As technology continues to shape our world, understanding the foundations and evolution of operating systems remains paramount. Join Pravash Chandra Das on this illuminating journey through the heart of computing. 🌟
Columbus Data & Analytics Wednesdays - June 2024
Columbus Data & Analytics Wednesdays, June 2024 with Maria Copot 20
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdf
Discover how MongoDB Atlas and vector search technology can revolutionize your application's search capabilities. This comprehensive presentation covers:
* What is Vector Search?
* Importance and benefits of vector search
* Practical use cases across various industries
* Step-by-step implementation guide
* Live demos with code snippets
* Enhancing LLM capabilities with vector search
* Best practices and optimization strategies
Perfect for developers, AI enthusiasts, and tech leaders. Learn how to leverage MongoDB Atlas to deliver highly relevant, context-aware search results, transforming your data retrieval process. Stay ahead in tech innovation and maximize the potential of your applications.
#MongoDB #VectorSearch #AI #SemanticSearch #TechInnovation #DataScience #LLM #MachineLearning #SearchTechnology
5th LF Energy Power Grid Model Meet-up Slides
5th Power Grid Model Meet-up
It is with great pleasure that we extend to you an invitation to the 5th Power Grid Model Meet-up, scheduled for 6th June 2024. This event will adopt a hybrid format, allowing participants to join us either through an online Mircosoft Teams session or in person at TU/e located at Den Dolech 2, Eindhoven, Netherlands. The meet-up will be hosted by Eindhoven University of Technology (TU/e), a research university specializing in engineering science & technology.
Power Grid Model
The global energy transition is placing new and unprecedented demands on Distribution System Operators (DSOs). Alongside upgrades to grid capacity, processes such as digitization, capacity optimization, and congestion management are becoming vital for delivering reliable services.
Power Grid Model is an open source project from Linux Foundation Energy and provides a calculation engine that is increasingly essential for DSOs. It offers a standards-based foundation enabling real-time power systems analysis, simulations of electrical power grids, and sophisticated what-if analysis. In addition, it enables in-depth studies and analysis of the electrical power grid’s behavior and performance. This comprehensive model incorporates essential factors such as power generation capacity, electrical losses, voltage levels, power flows, and system stability.
Power Grid Model is currently being applied in a wide variety of use cases, including grid planning, expansion, reliability, and congestion studies. It can also help in analyzing the impact of renewable energy integration, assessing the effects of disturbances or faults, and developing strategies for grid control and optimization.
What to expect
For the upcoming meetup we are organizing, we have an exciting lineup of activities planned:
-Insightful presentations covering two practical applications of the Power Grid Model.
-An update on the latest advancements in Power Grid -Model technology during the first and second quarters of 2024.
-An interactive brainstorming session to discuss and propose new feature requests.
-An opportunity to connect with fellow Power Grid Model enthusiasts and users.
Artificial Intelligence for XMLDevelopment
In the rapidly evolving landscape of technologies, XML continues to play a vital role in structuring, storing, and transporting data across diverse systems. The recent advancements in artificial intelligence (AI) present new methodologies for enhancing XML development workflows, introducing efficiency, automation, and intelligent capabilities. This presentation will outline the scope and perspective of utilizing AI in XML development. The potential benefits and the possible pitfalls will be highlighted, providing a balanced view of the subject.
We will explore the capabilities of AI in understanding XML markup languages and autonomously creating structured XML content. Additionally, we will examine the capacity of AI to enrich plain text with appropriate XML markup. Practical examples and methodological guidelines will be provided to elucidate how AI can be effectively prompted to interpret and generate accurate XML markup.
Further emphasis will be placed on the role of AI in developing XSLT, or schemas such as XSD and Schematron. We will address the techniques and strategies adopted to create prompts for generating code, explaining code, or refactoring the code, and the results achieved.
The discussion will extend to how AI can be used to transform XML content. In particular, the focus will be on the use of AI XPath extension functions in XSLT, Schematron, Schematron Quick Fixes, or for XML content refactoring.
The presentation aims to deliver a comprehensive overview of AI usage in XML development, providing attendees with the necessary knowledge to make informed decisions. Whether you’re at the early stages of adopting AI or considering integrating it in advanced XML development, this presentation will cover all levels of expertise.
By highlighting the potential advantages and challenges of integrating AI with XML development tools and languages, the presentation seeks to inspire thoughtful conversation around the future of XML development. We’ll not only delve into the technical aspects of AI-powered XML development but also discuss practical implications and possible future directions.
Recently uploaded (20)
Monitoring and Managing Anomaly Detection on OpenShift.pdf
Monitoring and Managing Anomaly Detection on OpenShift.pdf
Best 20 SEO Techniques To Improve Website Visibility In SERP
Best 20 SEO Techniques To Improve Website Visibility In SERP
Presentation of the OECD Artificial Intelligence Review of Germany
Presentation of the OECD Artificial Intelligence Review of Germany
Energy Efficient Video Encoding for Cloud and Edge Computing Instances
Energy Efficient Video Encoding for Cloud and Edge Computing Instances
Overcoming the PLG Trap: Lessons from Canva's Head of Sales & Head of EMEA Da...
Overcoming the PLG Trap: Lessons from Canva's Head of Sales & Head of EMEA Da...
Letter and Document Automation for Bonterra Impact Management (fka Social Sol...
Letter and Document Automation for Bonterra Impact Management (fka Social Sol...
Introduction of Cybersecurity with OSS at Code Europe 2024
Introduction of Cybersecurity with OSS at Code Europe 2024
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
Building Production Ready Search Pipelines with Spark and Milvus
Building Production Ready Search Pipelines with Spark and Milvus
GraphRAG for Life Science to increase LLM accuracy
GraphRAG for Life Science to increase LLM accuracy
Operating System Used by Users in day-to-day life.pptx
Operating System Used by Users in day-to-day life.pptx
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdf
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdf
Rally - How to use it
- 1. Rally - How To Use It aka “Why absolutely everything you do with it is wrong”
- 2. What is Rally? • A tool for managing SCRUM • If you don’t use SCRUM, you’re doing it wrong.
- 3. Some Terms • Product Backlog • Features/Stories • Iterations • Releases • Test Plans • Defects
- 4. Project Inception • Work out a couple of themes for a project • State those themes as stories • Create a backlog for the project • Put those stories in the backlog
- 5. What’s the Backlog for? • Stories that haven’t yet: • been defined • been estimated • been prioritised • You should have multiple backlogs
- 6. Story Hierarchies • Stories can have sub-stories • Sub-stories elaborate and expand the parent story • Keep breaking stories up until you hit the 1-3 day mark • Keep breaking stories up until acceptance criteria are small
- 7. Make A Booking Find A Room Pick The Dates Pay With Credit Card Obtain Card Details Charge Credit Card Handle Declined Cards Enter Guest Details Pay With Gift Voucher Validate Gift Voucher Balance Reduce Gift Voucher Balance Pay For Booking Record Accounting Details
- 8. Story Estimation • Guess-timates - “I think this will take XYZ” • Rule of 3 - keep guess-timates between 1 to 3 ‘units’ • Units are: • days, weeks, months, quarters, years
- 9. Task Estimations • Stories have tasks • Task are created when stories leave the backlog - NOT BEFORE! • Task estimations are “How long will this take me right now?” • Tasks do not depend on other stories • Tasks are in hours - Rule of 3 applies
- 10. Projects vs Teams • Projects have Backlogs • Projects have Releases • Projects DO NOT have iterations • Teams have iterations.
- 11. Iteration Planning • Populate team backlog • Pull in stories from project backlogs • Drag “defined” stories to iteration • Add tasks to stories • Don’t add too many stories • Don’t plan more than 2 iterations ahead
- 12. Rally As A Kanban Tool • See the Task Board
- 13. Release Planning • Plan releases around stories • Use the highest level story possible • All sub-stories automatically included • Release when stories are done
- 14. When in Doubt - Go Faster, Not Slower • Use shorter iterations - 1 week? • Focus on getting the process right • Use smaller releases - 1 story? • Keep team backlog short