Creating a backlog of user stories is pretty straight forward but it doesn't help you when it comes to decisions like what to build first, how to prioritize and groom the backlog, how to scope and plan the project, and how to visualize progress. The traditional backlog is simply too flat and often too long to help you see the bigger picture and make good decisions. User Story Mapping helps simplify all of these common project issues. By adding a third dimension to your backlog, your team will make better decisions about priorities, scope, and planning while improving your ability to visualize progress.
In this practical session I’ll cover the basics of user story mapping before walking you through case studies of how our teams are using this approach and the results we are achieving. I'll show you the before, during, and after pictures from several projects so that you can understand how our maps progress during the projects and how we use them to influence iterative development, promote good decision making, and visualize priorities, plans, scope and progress.
Agile 2009, Chicago: From CMMI and Isolation to Agile, Scrum, Lean and Collab...Mads Troels Hansen
Agile 2009 talk: Experience from implementing global big bang Scrum and building a kaizen culture. From long running projects, technical dept and integration nightmares to small batches, continuous integration and faster delivery of business value.
Too many organizations are using Scrum with focus on Delivery and do not consider discovery to maximize outcome and value. Scrum is an Empirical process where you embrace uncertainty to be more effective and while doing that you will also be more efficient utilizing the potential of the people involved.
Creating a backlog of user stories is pretty straight forward but it doesn't help you when it comes to decisions like what to build first, how to prioritize and groom the backlog, how to scope and plan the project, and how to visualize progress. The traditional backlog is simply too flat and often too long to help you see the bigger picture and make good decisions. User Story Mapping helps simplify all of these common project issues. By adding a third dimension to your backlog, your team will make better decisions about priorities, scope, and planning while improving your ability to visualize progress.
In this practical session I’ll cover the basics of user story mapping before walking you through case studies of how our teams are using this approach and the results we are achieving. I'll show you the before, during, and after pictures from several projects so that you can understand how our maps progress during the projects and how we use them to influence iterative development, promote good decision making, and visualize priorities, plans, scope and progress.
Agile 2009, Chicago: From CMMI and Isolation to Agile, Scrum, Lean and Collab...Mads Troels Hansen
Agile 2009 talk: Experience from implementing global big bang Scrum and building a kaizen culture. From long running projects, technical dept and integration nightmares to small batches, continuous integration and faster delivery of business value.
Too many organizations are using Scrum with focus on Delivery and do not consider discovery to maximize outcome and value. Scrum is an Empirical process where you embrace uncertainty to be more effective and while doing that you will also be more efficient utilizing the potential of the people involved.
One of the values of the Agile manifesto is working software over comprehensive documentation. However many agile teams think that now we are Agile we don’t need to document. Come to this session to learn about lightweight documentation and how to strike a sensible balance between working software and documentation. Learn which documents are necessary and which documents you can do without as well. Learn about JIT lightweight alternatives to our tradition documentation set. Leave with specific techniques to evaluate the value of each document along with recommended alternatives.
Agile Requirements - Journey of a User StoryCara Turner
This talk is an experience report on how we've used agile and lean requirements practices like story mapping, user stories, mockups, scenarios and sprint review feedback, on a real project.
It is not theory-based, but rather tells the warts-and-all real story, with a number of photos and screenshots, and detailed discussions of benefits and drawbacks, to give an idea of what it really felt like.
YouTube video of the talk: http://www.youtube.com/watch?v=iUIWLNiGYEk
Talk description:
How do agile requirements work? Where does documentation fit in?
For many of us, the transition from the security of upfront analysis and detailed specification documents to ‘doing agile’ and embracing the process of discovery is a terrifying prospect. Agile theories don’t readily address the concern ‘how will we know where we’re going if we don’t start with a Business Requirement Specification?’
In this talk I will take the audience on the journey of a real customer requirement from inception to delivery, seeing how the user stories evolved over time.
Starting at the beginning I’ll take you through how the user need was elaborated into features, stories and scenarios to become released software, and how feedback from customer interaction continued to shape it.
As we go along, we’ll see how the documentation built itself, and how it compares with the traditional Business Requirement Specification document.
With a little bit of theory and a lot of real world experience, we’ll also cover questions like “How can we be sure we’ll cover everything?” and “How do we overcome our uncertainty?”
Agile requirement gathering and elicitation techniques will be explained on this presentation. It is useful for Business Analysts and Agile practioners.
Defining user profiles is a key actiovity when designing interactive systems.
"Personas" technique is an excellent way for describing these user profiles.
Gathering and defining software requirements is difficult. One Agile technique to help address this challenge is writing user stories, which are short descriptions of functions that an end-user would want. While user stories help convert concepts into functions, writing good user stories is easier said than done.
What you’ll learn in this presentation:
• The basics of user stories.
• How user stories fit into the overall Agile planning process.
• How to write a user story.
Managing Requirements in Agile Development - Best Practices for Tool-Based Re...pd7.group
Agile software development leverages requirements management (RM) and offers many improvement opportunities for established RM practices. At the same time, agile RM must often be adopted to its specific application contexts and be combined with established RM. This is especially true for more complex areas like continuous product development and integrated hardware/software systems.
This presentation provides a brief overview of requirements management in the agile development lifecycle using methods like Scrum, XP, and Kanban. It introduces agile RM practices such as user stories and the Scaled Agile Framework (SAFeTM). Using examples from requirements tool Jama, the presentation illustrates how tool infrastructure can effectively support agile requirements management.
Contents of the presentation are:
- What is agile development? What is agile requirements management?
- Definition and agreement on agile user stories
- Requirements reviews & collaboration
- The interaction of requirements and tests in agile development
- Transition to agile RM
This presentation covers the why, who, what and when of writing requirements for Agile projects. Then we look at an example and how we can use mindmapping to brainstorm
This was a 1h very interactive session at NYC Scrum User Group on May 19, 2016, to talk about how to split user stories. These slides just set the stage, most was talk not recorded here.
Mark Logic Digital Publishing Summit, KelloggDave Kellogg
Slides from my presentation at the Mark Logic Digital Publishing Summit at The Plaza Hotel in NYC on 12/10/09. Topics include trends re-shaping the media and software information infrastructure.
One of the values of the Agile manifesto is working software over comprehensive documentation. However many agile teams think that now we are Agile we don’t need to document. Come to this session to learn about lightweight documentation and how to strike a sensible balance between working software and documentation. Learn which documents are necessary and which documents you can do without as well. Learn about JIT lightweight alternatives to our tradition documentation set. Leave with specific techniques to evaluate the value of each document along with recommended alternatives.
Agile Requirements - Journey of a User StoryCara Turner
This talk is an experience report on how we've used agile and lean requirements practices like story mapping, user stories, mockups, scenarios and sprint review feedback, on a real project.
It is not theory-based, but rather tells the warts-and-all real story, with a number of photos and screenshots, and detailed discussions of benefits and drawbacks, to give an idea of what it really felt like.
YouTube video of the talk: http://www.youtube.com/watch?v=iUIWLNiGYEk
Talk description:
How do agile requirements work? Where does documentation fit in?
For many of us, the transition from the security of upfront analysis and detailed specification documents to ‘doing agile’ and embracing the process of discovery is a terrifying prospect. Agile theories don’t readily address the concern ‘how will we know where we’re going if we don’t start with a Business Requirement Specification?’
In this talk I will take the audience on the journey of a real customer requirement from inception to delivery, seeing how the user stories evolved over time.
Starting at the beginning I’ll take you through how the user need was elaborated into features, stories and scenarios to become released software, and how feedback from customer interaction continued to shape it.
As we go along, we’ll see how the documentation built itself, and how it compares with the traditional Business Requirement Specification document.
With a little bit of theory and a lot of real world experience, we’ll also cover questions like “How can we be sure we’ll cover everything?” and “How do we overcome our uncertainty?”
Agile requirement gathering and elicitation techniques will be explained on this presentation. It is useful for Business Analysts and Agile practioners.
Defining user profiles is a key actiovity when designing interactive systems.
"Personas" technique is an excellent way for describing these user profiles.
Gathering and defining software requirements is difficult. One Agile technique to help address this challenge is writing user stories, which are short descriptions of functions that an end-user would want. While user stories help convert concepts into functions, writing good user stories is easier said than done.
What you’ll learn in this presentation:
• The basics of user stories.
• How user stories fit into the overall Agile planning process.
• How to write a user story.
Managing Requirements in Agile Development - Best Practices for Tool-Based Re...pd7.group
Agile software development leverages requirements management (RM) and offers many improvement opportunities for established RM practices. At the same time, agile RM must often be adopted to its specific application contexts and be combined with established RM. This is especially true for more complex areas like continuous product development and integrated hardware/software systems.
This presentation provides a brief overview of requirements management in the agile development lifecycle using methods like Scrum, XP, and Kanban. It introduces agile RM practices such as user stories and the Scaled Agile Framework (SAFeTM). Using examples from requirements tool Jama, the presentation illustrates how tool infrastructure can effectively support agile requirements management.
Contents of the presentation are:
- What is agile development? What is agile requirements management?
- Definition and agreement on agile user stories
- Requirements reviews & collaboration
- The interaction of requirements and tests in agile development
- Transition to agile RM
This presentation covers the why, who, what and when of writing requirements for Agile projects. Then we look at an example and how we can use mindmapping to brainstorm
This was a 1h very interactive session at NYC Scrum User Group on May 19, 2016, to talk about how to split user stories. These slides just set the stage, most was talk not recorded here.
Mark Logic Digital Publishing Summit, KelloggDave Kellogg
Slides from my presentation at the Mark Logic Digital Publishing Summit at The Plaza Hotel in NYC on 12/10/09. Topics include trends re-shaping the media and software information infrastructure.
Agile: It's not just for engineers anymore!Mark Congiusta
Presentation at the Lean-Agile@Cisco 2013 Conference discussing best practices for including user experience teams into Agile software development methodology.
This is a talk on experiences using agile techniques to manage projects in a number of businesses.
For more details see http://www.coclarity.com/blog/2009/11/speaking-at-leroei-event-on-agile-management/
Maven Application Lifecycle Management for Alfrescoguest67a9ba
Presentation about the Maven way to manage Alfresco customizations, using the Maven Alfresco Archetypes (http://wiki.alfresco.com/wiki/Managing_Alfresco_Lifecyle_with_Maven) by Gabriele Columbro (http://mindthegab.com/).
Automating Oracle Database deployment with Amazon Web Services, fabric, and botomjbommar
Have credit card, need database? In this talk, I'll show you how to deploy your own Oracle 11gR2 sandbox with a single keystroke (and I don't mean RDS). Along the way, we'll learn about Infrastructure-as-a-Service with boto, provisioning tools like fabric, and Oracle response files. When we're done, we'll have a repeatable, ten-minute process that can deliver a server as cheap as $5/day or as powerful as 40k IOPS and 2.6GB/s throughput. More importantly, we'll understand what the big deal about IaaS and automated provisioning really is, and how enterprise products like Oracle can still fit comfortably in the space.
Achieving Scale With Messaging And The Cloudgojkoadzic
From the Gaming Scalability event, June 2009 in London (http://gamingscalability.org).
Tony Garnock Jones presents RabbitMQ and talks about scaling with messaging in the clouds.
Design, Development and Evaluation of a Library's Enquiry Automatic Feedback ...Nurhazman Abdul Aziz
Library Enquiry Automatic Feedback pools all library-related questions and answers in one location. This is a postgraduate dissertation project. For more information, please check out at http://hazmanaziz.com
XP Day 2009 (London) - Patterns For Successful Distributed Development Xpday ...
User Story Mapping Daug 09062009
1. User Story Mapping
fast introduction
Danish Agile User Group
9/6-2009
Mads.Troels.Hansen@BestBrains.dk
2. Why User Story Mapping?
1. Dependencies between stories
2. Prioritize and considering business
workflow
3. One view to more easy understand
the end-to-end use of the system
4. Release planning