User story mapping is an intuitive way to build and organize a product backlog. During this session you’ll get hands-on experience building a user story map. You’ll learn:
How story mapping drives productive conversations with users and stakeholders.
How to plan incremental releases of your product using minimal holistic slices that deliver value at each product release.
Secrets to effective prioritization for both planning releases, and figuring out what to build next.
Tactical management of your backlog as you grow your working software to releasability.
The backlog building and managing strategies in this session will take you well beyond the agile basics.
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.
Writing Good User Stories (Hint: It's not about writing)one80
User stories are typically the foundation of the Product Backlog. However, the original purpose has been lost. This is from a presentation that was given to help remind everyone of what User Stories are, and what they aren't. The purpose of User Stories is to drive conversations, not to hand "requirements" from one group to the next.
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.
Writing Good User Stories (Hint: It's not about writing)one80
User stories are typically the foundation of the Product Backlog. However, the original purpose has been lost. This is from a presentation that was given to help remind everyone of what User Stories are, and what they aren't. The purpose of User Stories is to drive conversations, not to hand "requirements" from one group to the next.
User Story Mapping, Discover the whole storyJeff Patton
Variations of these slides have been used in a variety of talks.
These slides support discussions on why stories work, and when they don't. And, on story mapping, how and why it works.
A talk I gave at Google on Strategy and Product Discovery
We discussed:
Discovering Features and Products (Product Strategy)
Discovering Products and Product Lines (Product Line / Company Strategy)
Marty Cagan: Using High Fidelity Prototypes for Product Discovery
User Story Mapping workshop facilitated at NYC Scrum User group.
Inspired by Jeff Patton's book "User Story Mapping. Discover the Whole Story, Build the Right Product"
http://shop.oreilly.com/product/0636920033851.do
Lean Startup + Story Mapping = Awesome Products FasterBrad Swanson
To deliver the right outcomes, you need to learn your customers needs and validate your assumptions as early as possible. This means getting an early version of your product completed to start testing, validating and improving. This session will demonstrate how to combine Lean Startup and User Story Mapping techniques to determine where to start and how to learn early and often.
Participants will start with a partially completed Lean Canvas to flesh out and then define a product roadmap by building a Story Map. We will use Lean Startup concepts of Minimal Viable Product (MVP) and validated learning to focus on outcome over output.
Learning objectives:
Understand the importance of accelerated learning and techniques to achieve it
How a Lean Canvas can help shape your product vision and MVP
How to build a story map to create a product roadmap
How to use a story map to validate your users' journey
User Story Mapping Workshop (Design Skills 2016)Bartosz Mozyrko
User Story Mapping (USM) is a top-down approach of gathering "requirements" in agile environments.
"A user story map arranges user stories into a useful model to help understand the functionality of the system, identify holes and omissions in your backlog, and effectively plan holistic releases that deliver value to users and business with each release (from Jeff Patton's The New User Story Backlog Is a Map)."
Overview
- What is a User Story?
- User Story template
- examples of User Stories
- User Story Checklist
- Why not tasks?
- What is Acceptance Criteria?
- Examples of Acceptance Criteria
- Acceptance Criteria checklist
Behind every great product is a great team doing work in a way that guarantees results. They are following a roadmap from the starting point to the end product. But a product roadmap can be elusive. This talk addresses why it is important and presents an approach to make one.
Do you want to write great User Stories that provide the vehicle for conversation and confirmation that we build the right thing? Do you struggle with splitting stories so that they still provide business value but can be accomplished within a fraction of your iteration? We will do a quick refresher on User Story formatting to include Acceptance Criteria. Additionally we will learn techniques for splitting stories in this interactive workshop.
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.
At the start of a project or start of a major release, we always face the problem of "How do we break down this big release into stories?" " How do I move from this vision to lower level details in user stories?". My workshop & presentation at the #India Agile Week 2013 Pune was focussed on providing answers to this. This presentation provides a way to move from high level vision to user stories using Story Map.
Arlen Bankston
Arlen is an established leader in the application and evolution of process management methodologies such as Lean, Six Sigma and BPM, as well as Agile software development processes such as Extreme Programming (XP) and Scrum. He is a Lean Six Sigma Master Black Belt and Certified ScrumMaster Trainer. He also has twelve years of experience in product design, leveraging principles of information architecture, interaction design and usability to develop innovative products that meet customers’ expressed and unspoken needs. Arlen has led Agile and Lean deployment and managed process improvement projects at clients such as Capital One, T. Rowe Price, Freddie Mac, and the Armed Forces Benefits Association. Arlen’s recent work has centered on combining Lean Six Sigma process improvement methods with Agile execution to dramatically improve both the speed and quality of business results. He has also led the integration of interaction design and usability practices into Agile methodologies, presenting and training frequently at both industry conferences and to Fortune 100 clients.
User Story Mapping, Discover the whole storyJeff Patton
Variations of these slides have been used in a variety of talks.
These slides support discussions on why stories work, and when they don't. And, on story mapping, how and why it works.
A talk I gave at Google on Strategy and Product Discovery
We discussed:
Discovering Features and Products (Product Strategy)
Discovering Products and Product Lines (Product Line / Company Strategy)
Marty Cagan: Using High Fidelity Prototypes for Product Discovery
User Story Mapping workshop facilitated at NYC Scrum User group.
Inspired by Jeff Patton's book "User Story Mapping. Discover the Whole Story, Build the Right Product"
http://shop.oreilly.com/product/0636920033851.do
Lean Startup + Story Mapping = Awesome Products FasterBrad Swanson
To deliver the right outcomes, you need to learn your customers needs and validate your assumptions as early as possible. This means getting an early version of your product completed to start testing, validating and improving. This session will demonstrate how to combine Lean Startup and User Story Mapping techniques to determine where to start and how to learn early and often.
Participants will start with a partially completed Lean Canvas to flesh out and then define a product roadmap by building a Story Map. We will use Lean Startup concepts of Minimal Viable Product (MVP) and validated learning to focus on outcome over output.
Learning objectives:
Understand the importance of accelerated learning and techniques to achieve it
How a Lean Canvas can help shape your product vision and MVP
How to build a story map to create a product roadmap
How to use a story map to validate your users' journey
User Story Mapping Workshop (Design Skills 2016)Bartosz Mozyrko
User Story Mapping (USM) is a top-down approach of gathering "requirements" in agile environments.
"A user story map arranges user stories into a useful model to help understand the functionality of the system, identify holes and omissions in your backlog, and effectively plan holistic releases that deliver value to users and business with each release (from Jeff Patton's The New User Story Backlog Is a Map)."
Overview
- What is a User Story?
- User Story template
- examples of User Stories
- User Story Checklist
- Why not tasks?
- What is Acceptance Criteria?
- Examples of Acceptance Criteria
- Acceptance Criteria checklist
Behind every great product is a great team doing work in a way that guarantees results. They are following a roadmap from the starting point to the end product. But a product roadmap can be elusive. This talk addresses why it is important and presents an approach to make one.
Do you want to write great User Stories that provide the vehicle for conversation and confirmation that we build the right thing? Do you struggle with splitting stories so that they still provide business value but can be accomplished within a fraction of your iteration? We will do a quick refresher on User Story formatting to include Acceptance Criteria. Additionally we will learn techniques for splitting stories in this interactive workshop.
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.
At the start of a project or start of a major release, we always face the problem of "How do we break down this big release into stories?" " How do I move from this vision to lower level details in user stories?". My workshop & presentation at the #India Agile Week 2013 Pune was focussed on providing answers to this. This presentation provides a way to move from high level vision to user stories using Story Map.
Arlen Bankston
Arlen is an established leader in the application and evolution of process management methodologies such as Lean, Six Sigma and BPM, as well as Agile software development processes such as Extreme Programming (XP) and Scrum. He is a Lean Six Sigma Master Black Belt and Certified ScrumMaster Trainer. He also has twelve years of experience in product design, leveraging principles of information architecture, interaction design and usability to develop innovative products that meet customers’ expressed and unspoken needs. Arlen has led Agile and Lean deployment and managed process improvement projects at clients such as Capital One, T. Rowe Price, Freddie Mac, and the Armed Forces Benefits Association. Arlen’s recent work has centered on combining Lean Six Sigma process improvement methods with Agile execution to dramatically improve both the speed and quality of business results. He has also led the integration of interaction design and usability practices into Agile methodologies, presenting and training frequently at both industry conferences and to Fortune 100 clients.
Intro to User Journey Maps for Building Better Websites - Cornell Drupal Camp...Anthony D. Paul
You’ve asked the right questions and maybe you have some personas. There’s a heap of feature requests from your client and a whole lot of content to organize into a sitemap (IA) document and wireframes. However, something’s not sitting right and you wonder how the site fits into the bigger customer journey with the client’s brand, business, and products.
In this talk, I’ll show you how to get started with taking all of that subject matter expertise you’ve been collecting in your mind, and to convert it into one of several useful types of journey maps. I’ll share process, examples, context on how they fit into a larger project, and show how they help bring agreement among your client decision-makers.
• Understand the benefits of thinking through a user journey outside of your website.
• See the variety of types of journey maps and identify where and when to use them.
• Build and use journey maps to shape client conversations and audit decisions.
Passionate Product Ownership is an experience that will expose you to new ways of thinking and working.You’ll learn the details you need to fulfill or support the Scrum Product Owner role in this course. But, we believe that understanding the role and its requirements isn’t enough to be successful. So, in this course, you’ll engage in a process simulation that models a different way of working, a way that emphasizes working collaboratively as a balanced core team, and having a user-centric product design approach.
What’s taught in the Agile Passionate Product Ownership is based on the underlying philosophy that you should:
Judge the success of your process based on the satisfaction of your users and customers with your product.
A prioritized user story backlog helps to understand what to do next, but is a difficult tool for understanding what your whole system is intended to do. A user story map arranges user stories into a useful model to help understand the functionality of the system, identify holes and omissions in your backlog, and effectively plan holistic releases that delivery value to users and business with each release.
Maximizing Your Office 365 Investments With OneDriveNetwoven Inc.
Learn how to maximize OneDrive with Office 365 and have virtually ubiquitous access to open, edit and share data from anywhere. Also, Office 365 users can now stop discriminating about which files or data deserve to occupy the cloud and which should remain local.
Key Takeaways:
• Why use OneDrive with Office 365
• Comparison between OneDrive and other cloud storage products
• OneDrive Migration
• Integration with Office 365
These tales relate successful attempts at making improvements. They are described mostly in the order in which they occurred, from my time working in an Agile culture. The tales are about: Creating the Motivation to Pair Program, Staying Focused at Stand-up, Keeping Progress High and Questions Low, Reassigning Points to Validate Estimation, Admitting to the Real Date, Dealing With an Overwhelming Amount of Work, Gauging the Rate of Progress, Figuring Out How to Construct Teams, Finding Predictability in the Velocity, Allowing for Cross-Functional Teams
What do you get when user experience drives the agile process? Dual-Track Agile, where the features of the product are discovered alongside the development of the product itself. This session will explain what dual-track agile is, the benefits of dual-track agile, the role of UX, and what to expect. It will focus on the discovery cycle, the role of validated hypotheses and assumptions and how UX uniquely contributes to this invaluable process.
You may have heard that Microsoft NextGen Portals are coming. And maybe you are already using tools like Delve that are the first generation of these NextGen Portals. But many questions around NextGen Portals have gone unanswered.
Get the answers you need to better understand and use Microsoft NextGen Portals.
In this webinar, Portal Solutions’ Daniel Cohen-Dumani and Josh Steiner discuss the most frequently asked questions about NextGen Portals.
- What are NextGen Portals anyway?
- Why are NextGen Portals important?
- When are NextGen Portals coming?
What Am I Buying? Understanding Website Cost and TechnologyIan Mariano
Your website is a crucial part of your brand experience, and the decisions you make can make or break its effectiveness. Technology decisions are key to a successful site—having insight into the technology and its associated costs can help you make choices that benefit your site and your organization.
[#DevRelAsia Keynote 2020] Developer Centric Design for Better ExperienceTomomi Imura
Tomomi Imura talks about improving the developer experience of technical content & docs and her own experiences from the most recent project at Microsoft and her previous work at Slack.
SPS Jersey 2014 - Creating a Great User Experience in SharePointMarc D Anderson
Building solutions in SharePoint isn’t simply about getting the functionality right based on the business requirements. Developers must think about the entire user experience (UX), which goes far beyond the technical aspects of the solution. It’s no longer good enough to meet the specifications. We must exceed them in terms of usability. This takes many developers out of their comfort zones and into the messy world of end users.
In this interactive session, we’ll discuss questions like:
* How should the user feel when they use this piece of functionality?
* Will they perceive that this functionality saves them work or creates new work?
* How will the functionality compare to what they see on the consumer Web?
* How can we use technologies which haven’t historically been considered mainstream SharePoint developer tools (like jQuery and CSS) to make SharePoint feel more like the sites people love?
Whether you're an executive sponsor, end user, power user, developer, or IT Pro, there are bound to be some takeaways for you as you adapt SharePoint to meet your organization's needs.
How to design enterprise apps that sellInVision App
Your customers expect great UX from your enterprise app. So do you. With gnarly legacy code to wrangle, complex requirements to manage, and results to deliver, you need to have the right process. Arm yourself with techniques and methods to craft successful enterprise apps.
This in-depth webinar from Jessica Tiao of Kissmetrics gives you the tools, advice, and best practices you need to succeed.
An Introduction To Software Development - Software Development Midterm ReviewBlue Elephant Consulting
This presentation is a part of the COP2271C college level course taught at the Florida Polytechnic University located in Lakeland Florida. The purpose of this course is to introduce Freshmen students to both the process of software development and to the Python language.
The course is one semester in length and meets for 2 hours twice a week. The Instructor is Dr. Jim Anderson.
A video of Dr. Anderson using these slides is available on YouTube at:
http://youtu.be/IgrPAlFVWbw
24 Hours of UX, 2023: Preventing the FutureJoshua Randall
On our current trajectory, the future of UX design will look much like the present, only worse. The gold rush mentality towards UX design as a “career” combined with Gresham’s Law (“bad money drives out good”) applied to design combined with automation from software platforms means we are increasing the pace at which bad designs proliferate. In this talk Joshua Randall will cite data from larger research companies like Baymard and Nielsen Norman Group as well as draw on examples from his career to paint a picture of the coming dystopia.
What am i buying understanding website cost and technology 17 ntcIan Mariano
My presentation at the Nonprofit Technical Network Conference 2017. Technology cost is more than financial. In this presentation I present a way for people to shift how they think about cost, and a framework for assessing cost, an with that knowledge, finding and engaging with partners to deliver value.
Elevating the Business Analyst with the lens of Human Centered Design Thinking.
Learn how Human Centered Thinking and User Experience Design can directly address common software pitfalls.
It's Better To Have a Permanent Income Than to Be Fascinating: Killer Feature...Ultan O'Broin
Presented at Product Camp Dublin 2018. Presentation on picking the right thing to design, right. The Jobs To Be Done framework trumps UX profiles and personas. Keeping it simple, wire-framing best practices, and Lean Startup methodologies included!
Similar to User Story Maps: Secrets for Better Backlogs and Planning (20)
Code reviews are vital for ensuring good code quality. They serve as one of our last lines of defense against bugs and subpar code reaching production.
Yet, they often turn into annoying tasks riddled with frustration, hostility, unclear feedback and lack of standards. How can we improve this crucial process?
In this session we will cover:
- The Art of Effective Code Reviews
- Streamlining the Review Process
- Elevating Reviews with Automated Tools
By the end of this presentation, you'll have the knowledge on how to organize and improve your code review proces
Paketo Buildpacks : la meilleure façon de construire des images OCI? DevopsDa...Anthony Dahanne
Les Buildpacks existent depuis plus de 10 ans ! D’abord, ils étaient utilisés pour détecter et construire une application avant de la déployer sur certains PaaS. Ensuite, nous avons pu créer des images Docker (OCI) avec leur dernière génération, les Cloud Native Buildpacks (CNCF en incubation). Sont-ils une bonne alternative au Dockerfile ? Que sont les buildpacks Paketo ? Quelles communautés les soutiennent et comment ?
Venez le découvrir lors de cette session ignite
In software engineering, the right architecture is essential for robust, scalable platforms. Wix has undergone a pivotal shift from event sourcing to a CRUD-based model for its microservices. This talk will chart the course of this pivotal journey.
Event sourcing, which records state changes as immutable events, provided robust auditing and "time travel" debugging for Wix Stores' microservices. Despite its benefits, the complexity it introduced in state management slowed development. Wix responded by adopting a simpler, unified CRUD model. This talk will explore the challenges of event sourcing and the advantages of Wix's new "CRUD on steroids" approach, which streamlines API integration and domain event management while preserving data integrity and system resilience.
Participants will gain valuable insights into Wix's strategies for ensuring atomicity in database updates and event production, as well as caching, materialization, and performance optimization techniques within a distributed system.
Join us to discover how Wix has mastered the art of balancing simplicity and extensibility, and learn how the re-adoption of the modest CRUD has turbocharged their development velocity, resilience, and scalability in a high-growth environment.
Software Engineering, Software Consulting, Tech Lead.
Spring Boot, Spring Cloud, Spring Core, Spring JDBC, Spring Security,
Spring Transaction, Spring MVC,
Log4j, REST/SOAP WEB-SERVICES.
Experience our free, in-depth three-part Tendenci Platform Corporate Membership Management workshop series! In Session 1 on May 14th, 2024, we began with an Introduction and Setup, mastering the configuration of your Corporate Membership Module settings to establish membership types, applications, and more. Then, on May 16th, 2024, in Session 2, we focused on binding individual members to a Corporate Membership and Corporate Reps, teaching you how to add individual members and assign Corporate Representatives to manage dues, renewals, and associated members. Finally, on May 28th, 2024, in Session 3, we covered questions and concerns, addressing any queries or issues you may have.
For more Tendenci AMS events, check out www.tendenci.com/events
Innovating Inference - Remote Triggering of Large Language Models on HPC Clus...Globus
Large Language Models (LLMs) are currently the center of attention in the tech world, particularly for their potential to advance research. In this presentation, we'll explore a straightforward and effective method for quickly initiating inference runs on supercomputers using the vLLM tool with Globus Compute, specifically on the Polaris system at ALCF. We'll begin by briefly discussing the popularity and applications of LLMs in various fields. Following this, we will introduce the vLLM tool, and explain how it integrates with Globus Compute to efficiently manage LLM operations on Polaris. Attendees will learn the practical aspects of setting up and remotely triggering LLMs from local machines, focusing on ease of use and efficiency. This talk is ideal for researchers and practitioners looking to leverage the power of LLMs in their work, offering a clear guide to harnessing supercomputing resources for quick and effective LLM inference.
SOCRadar Research Team: Latest Activities of IntelBrokerSOCRadar
The European Union Agency for Law Enforcement Cooperation (Europol) has suffered an alleged data breach after a notorious threat actor claimed to have exfiltrated data from its systems. Infamous data leaker IntelBroker posted on the even more infamous BreachForums hacking forum, saying that Europol suffered a data breach this month.
The alleged breach affected Europol agencies CCSE, EC3, Europol Platform for Experts, Law Enforcement Forum, and SIRIUS. Infiltration of these entities can disrupt ongoing investigations and compromise sensitive intelligence shared among international law enforcement agencies.
However, this is neither the first nor the last activity of IntekBroker. We have compiled for you what happened in the last few days. To track such hacker activities on dark web sources like hacker forums, private Telegram channels, and other hidden platforms where cyber threats often originate, you can check SOCRadar’s Dark Web News.
Stay Informed on Threat Actors’ Activity on the Dark Web with SOCRadar!
A Comprehensive Look at Generative AI in Retail App Testing.pdfkalichargn70th171
Traditional software testing methods are being challenged in retail, where customer expectations and technological advancements continually shape the landscape. Enter generative AI—a transformative subset of artificial intelligence technologies poised to revolutionize software testing.
Developing Distributed High-performance Computing Capabilities of an Open Sci...Globus
COVID-19 had an unprecedented impact on scientific collaboration. The pandemic and its broad response from the scientific community has forged new relationships among public health practitioners, mathematical modelers, and scientific computing specialists, while revealing critical gaps in exploiting advanced computing systems to support urgent decision making. Informed by our team’s work in applying high-performance computing in support of public health decision makers during the COVID-19 pandemic, we present how Globus technologies are enabling the development of an open science platform for robust epidemic analysis, with the goal of collaborative, secure, distributed, on-demand, and fast time-to-solution analyses to support public health.
Globus Connect Server Deep Dive - GlobusWorld 2024Globus
We explore the Globus Connect Server (GCS) architecture and experiment with advanced configuration options and use cases. This content is targeted at system administrators who are familiar with GCS and currently operate—or are planning to operate—broader deployments at their institution.
OpenFOAM solver for Helmholtz equation, helmholtzFoam / helmholtzBubbleFoamtakuyayamamoto1800
In this slide, we show the simulation example and the way to compile this solver.
In this solver, the Helmholtz equation can be solved by helmholtzFoam. Also, the Helmholtz equation with uniformly dispersed bubbles can be simulated by helmholtzBubbleFoam.
First Steps with Globus Compute Multi-User EndpointsGlobus
In this presentation we will share our experiences around getting started with the Globus Compute multi-user endpoint. Working with the Pharmacology group at the University of Auckland, we have previously written an application using Globus Compute that can offload computationally expensive steps in the researcher's workflows, which they wish to manage from their familiar Windows environments, onto the NeSI (New Zealand eScience Infrastructure) cluster. Some of the challenges we have encountered were that each researcher had to set up and manage their own single-user globus compute endpoint and that the workloads had varying resource requirements (CPUs, memory and wall time) between different runs. We hope that the multi-user endpoint will help to address these challenges and share an update on our progress here.
Enhancing Research Orchestration Capabilities at ORNL.pdfGlobus
Cross-facility research orchestration comes with ever-changing constraints regarding the availability and suitability of various compute and data resources. In short, a flexible data and processing fabric is needed to enable the dynamic redirection of data and compute tasks throughout the lifecycle of an experiment. In this talk, we illustrate how we easily leveraged Globus services to instrument the ACE research testbed at the Oak Ridge Leadership Computing Facility with flexible data and task orchestration capabilities.
Globus Compute wth IRI Workflows - GlobusWorld 2024Globus
As part of the DOE Integrated Research Infrastructure (IRI) program, NERSC at Lawrence Berkeley National Lab and ALCF at Argonne National Lab are working closely with General Atomics on accelerating the computing requirements of the DIII-D experiment. As part of the work the team is investigating ways to speedup the time to solution for many different parts of the DIII-D workflow including how they run jobs on HPC systems. One of these routes is looking at Globus Compute as a way to replace the current method for managing tasks and we describe a brief proof of concept showing how Globus Compute could help to schedule jobs and be a tool to connect compute at different facilities.
Why React Native as a Strategic Advantage for Startup Innovation.pdfayushiqss
Do you know that React Native is being increasingly adopted by startups as well as big companies in the mobile app development industry? Big names like Facebook, Instagram, and Pinterest have already integrated this robust open-source framework.
In fact, according to a report by Statista, the number of React Native developers has been steadily increasing over the years, reaching an estimated 1.9 million by the end of 2024. This means that the demand for this framework in the job market has been growing making it a valuable skill.
But what makes React Native so popular for mobile application development? It offers excellent cross-platform capabilities among other benefits. This way, with React Native, developers can write code once and run it on both iOS and Android devices thus saving time and resources leading to shorter development cycles hence faster time-to-market for your app.
Let’s take the example of a startup, which wanted to release their app on both iOS and Android at once. Through the use of React Native they managed to create an app and bring it into the market within a very short period. This helped them gain an advantage over their competitors because they had access to a large user base who were able to generate revenue quickly for them.
Field Employee Tracking System| MiTrack App| Best Employee Tracking Solution|...informapgpstrackings
Keep tabs on your field staff effortlessly with Informap Technology Centre LLC. Real-time tracking, task assignment, and smart features for efficient management. Request a live demo today!
For more details, visit us : https://informapuae.com/field-staff-tracking/
Providing Globus Services to Users of JASMIN for Environmental Data AnalysisGlobus
JASMIN is the UK’s high-performance data analysis platform for environmental science, operated by STFC on behalf of the UK Natural Environment Research Council (NERC). In addition to its role in hosting the CEDA Archive (NERC’s long-term repository for climate, atmospheric science & Earth observation data in the UK), JASMIN provides a collaborative platform to a community of around 2,000 scientists in the UK and beyond, providing nearly 400 environmental science projects with working space, compute resources and tools to facilitate their work. High-performance data transfer into and out of JASMIN has always been a key feature, with many scientists bringing model outputs from supercomputers elsewhere in the UK, to analyse against observational or other model data in the CEDA Archive. A growing number of JASMIN users are now realising the benefits of using the Globus service to provide reliable and efficient data movement and other tasks in this and other contexts. Further use cases involve long-distance (intercontinental) transfers to and from JASMIN, and collecting results from a mobile atmospheric radar system, pushing data to JASMIN via a lightweight Globus deployment. We provide details of how Globus fits into our current infrastructure, our experience of the recent migration to GCSv5.4, and of our interest in developing use of the wider ecosystem of Globus services for the benefit of our user community.
Your Digital Assistant.
Making complex approach simple. Straightforward process saves time. No more waiting to connect with people that matter to you. Safety first is not a cliché - Securely protect information in cloud storage to prevent any third party from accessing data.
Would you rather make your visitors feel burdened by making them wait? Or choose VizMan for a stress-free experience? VizMan is an automated visitor management system that works for any industries not limited to factories, societies, government institutes, and warehouses. A new age contactless way of logging information of visitors, employees, packages, and vehicles. VizMan is a digital logbook so it deters unnecessary use of paper or space since there is no requirement of bundles of registers that is left to collect dust in a corner of a room. Visitor’s essential details, helps in scheduling meetings for visitors and employees, and assists in supervising the attendance of the employees. With VizMan, visitors don’t need to wait for hours in long queues. VizMan handles visitors with the value they deserve because we know time is important to you.
Feasible Features
One Subscription, Four Modules – Admin, Employee, Receptionist, and Gatekeeper ensures confidentiality and prevents data from being manipulated
User Friendly – can be easily used on Android, iOS, and Web Interface
Multiple Accessibility – Log in through any device from any place at any time
One app for all industries – a Visitor Management System that works for any organisation.
Stress-free Sign-up
Visitor is registered and checked-in by the Receptionist
Host gets a notification, where they opt to Approve the meeting
Host notifies the Receptionist of the end of the meeting
Visitor is checked-out by the Receptionist
Host enters notes and remarks of the meeting
Customizable Components
Scheduling Meetings – Host can invite visitors for meetings and also approve, reject and reschedule meetings
Single/Bulk invites – Invitations can be sent individually to a visitor or collectively to many visitors
VIP Visitors – Additional security of data for VIP visitors to avoid misuse of information
Courier Management – Keeps a check on deliveries like commodities being delivered in and out of establishments
Alerts & Notifications – Get notified on SMS, email, and application
Parking Management – Manage availability of parking space
Individual log-in – Every user has their own log-in id
Visitor/Meeting Analytics – Evaluate notes and remarks of the meeting stored in the system
Visitor Management System is a secure and user friendly database manager that records, filters, tracks the visitors to your organization.
"Secure Your Premises with VizMan (VMS) – Get It Now"
3. 3comakers, LLC ::
Now and Later
3
Now and Later photo: Jay Malone via Flickr
http://www.flickr.com/photos/jcorduroy/3725077603/
Turn and talk with someone
at your table:
What challenges do you have
today with user stories?
If you’re not working with
agile development, what
challenges do you have with
project requirements?
5. 5comakers, LLC :: hello@comakewith.us
What we’ll cover
Stories and Story Maps
What’s a story map
Everything you need to know about stories, but were
afraid to ask
Story Mapping in Agile Process
Building the backbone
Filling in and validating
Prioritizing and planning
7. 7comakers, LLC :: hello@comakewith.us
A Story Map helps facilitate discussion
about user’s experience with our
product
Gary Levitt, owner & designer of Mad Mimi
7
details•smaller steps•alternative steps•UI details•technical details
details•smaller steps•alternative steps•UI details•technical details
workflow(from the user’s
perspective)
workflow(from the user’s
perspective)
backbone(gives structure to themap)
backbone(gives structure to themap)
product goals
(why build the
product)
product goals
(why build the
product)
users
(what are their goals)
users
(what are their goals)
8. 8comakers, LLC :: hello@comakewith.us
Story maps aren’t an invention, they’re a
pattern
David Hussman Story
Jamming
Narrative Journey
Map courtesy
Duncan Brown of
the Caplin Group
Indi Young’s
Mental Model
Todd ZakiWarfel’s
Task Analysis Grid
9. 9comakers, LLC :: hello@comakewith.us
Key concepts
Sketch a quick image/diagram for each, based on what you
remember
story map
backbone
other types of maps
10. 10
2comakers, LLC :: hello@comakewith.us
What you need to
know about user
stories
11. 11comakers, LLC :: hello@comakewith.ushttp://www.cakewrecks.blogspot.com
Specifying in writing
doesn’t work well
12. 12comakers, LLC :: hello@comakewith.us
user
Stories facilitate a conversation with a
goal of shared understanding
developer
13. 13comakers, LLC :: hello@comakewith.us
Stories have a simple lifecycle
! ?
Card
Conversation
!
Confirmation
Consequences
! ??
!
Construction
* Ron Jeffries coined the
3 C’s in Extreme
Programming Installed
14. 14
BA
comakers, LLC :: hello@comakewith.us
user
testerPM
UX Designer
Stories need to support lots of
conversations across lots of project roles
developer
business leader
15. 15comakers, LLC :: hello@comakewith.us
User Stories are boundary objects
Here’s the fine print on boundary objects:
“A boundary object is a concept in sociology to describe information used
in different ways by different communities. They are plastic, interpreted
differently across communities but with enough immutable content
to maintain integrity” --Wikipedia
“They are weakly structured in common use, and become strongly
structured in individual-site use. They may be abstract or concrete.
They have different meanings in different social worlds but their structure
is common enough to more than one world to make them recognizable
means of translation. The creation and management of boundary objects
is key in developing and maintaining coherence across intersecting social
worlds.”
-- Leigh & Griesemer
20. 20comakers, LLC :: hello@comakewith.us
Imagine the future
Who are the users and
what benefit do they get?
What will users do in the
future using your software?
Why should your
organization build the
software? What benefit
will they get?
21. 21comakers, LLC :: hello@comakewith.us
Stories gain detail over time and from
conversation - don’t add all your details at
once
Start with a short title
Add a concise description
some use this useful template:
As a [type of user]
I want to [perform some
task]
so that I can [reach some
goal]
Add other relevant notes,
specifications, or sketches
Before building software write
acceptance criteria (how do
we know when we’re done?)
22. That story’s
too big!
That story’s
too big!
Stories should describe
software that can be
built in a couple days
23. I’m not
really getting
what this
product is
about!
I’m not
really getting
what this
product is
about!
When considering a
product a story at a time
it’s easy to lose the big
picture
25. 25comakers, LLC :: hello@comakewith.us
user
product
manager
The natural “unit of measure” for stories
varies by conversation
BA or
UI Designer
developer
business
leader
26. release cycle
development
cycle
User Stories shrink in size and grow in
detail as they travel through a pipeline
Capabilities
or features
•Name
•Target customer or
user
•Value
Release-
sized stories
•Target release
•Relative size
•UI sketches
•Rough acceptance
tests
Stories for
upcoming
iterations
•Priority
•UI design
•Business rules
•Acceptance tests
Iteration-
sized stories
•Detailed
acceptance tests
•Small enough to
complete in an
iteration
Working
tested
software
•Meets the team’s
definition of done
Validated
product parts
•Vetted with customers
and users
•Evaluated for release
readiness
Minimal
releasable
software
•Generates value
from its use
29. 29comakers, LLC :: hello@comakewith.us
Key concepts
Ask someone to explain the one that stands out the most for them, then
switch and have them ask you.
agile user story
boundary object
output, outcome, &
impact
the canonical story
template
what, who, why
story size
the story funnel
30. 30comakers, LLC :: hello@comakewith.us
Story maps are built during a product
discovery phase
what:
who:
why:
what:
who:
why:
User Story Map
R1
User Story Map
R2
R3
Opportunity
Backlog
Contains valuable product
and feature ideas
Product
Discovery
Research, explore, validate
and plan delivery of potential
product solutions
Product Delivery
Iteratively and incrementally
build and validate product
solutions
what:
who:
why:
R2what:
who:
why:
R3what:
who:
why:
R1
User Story Map Product Backlog
Product
Goals
Simple
Personas
User Interface Sketch
32. 32comakers, LLC ::
Before mapping identify
relevant context
Business
Strategy
Customer
Segments
Users & user
goals
Product
usages
Regulatory
constraints
Legacy product
and architecture
?What else?
33. 33comakers, LLC :: hello@comakewith.us
What, who, and why
What: name the product,
feature, or capability you’re
thinking of
Who: name the choosers
and users who will buy and
use the resulting solution
Why: say how the
organization paying to build
the software benefits -
describes pains today or
desired outcomes
Collaboratively sketch simple
pragmatic personas
Stickyminds.com article: Pragmatic
Personas
http://www.stickyminds.com/s.asp?F=
Identify measurable product goals
http://agileproductdesign.com/writing/patton
34. 34comakers, LLC :: hello@comakewith.us
Build the backbone of
your map by:
1. Discussing experience
and then mapping
35. 35comakers, LLC :: hello@comakewith.us
Building a backlog as a story map is a
discussion about user experience, not user
stories
36. 36comakers, LLC :: hello@comakewith.us
Build the backbone of your
map by:
2. Brainstorming user’s
tasks then organizing
(Ask a group of users to list all
the things they do as part of a
business process)
38. 38comakers, LLC :: hello@comakewith.us
Build the backbone of your map
by:
3. Researching, observing,
designing, and then extracting
stories from a narrative
(A narrative like a use case or user
scenario describes what people do to
reach their goals. Extract the verb
phrases from a narrative)
39. 39comakers, LLC :: hello@comakewith.us
Harvest tasks from scenarios
Field Manager enters daily performance reports
The shift has just ended and his reps are coming up with their totals.
They have printed sheets with totals written on them. Steve
quickly looks them over and signs them off. His assistant
manager brings him other sheets with totals he’s signed off.
In between visits by reps, Steve opens his Field Manager
Workbench on his laptop. After logging in he sees today’s date
and the planned number of applications his reps should be
gathering – 180 for today.
He also sees yesterday’s numbers, and last week’s numbers, and
the last 30 days in graph that shows applications relative to
approval rate. Last week’s numbers were bad, and it’s the last
week of the month, so Steve knows he’s got to do well today.
Steve clicks “enter rep performance data.” He shuffles his reps
performance sheets and grabs the first one.
5. The date is defaulted to today, and the shift is defaulted to ‘morning’
since he hasn’t yet entered info for today. Steve begins to enter the
reps name, but after a few characters the system auto-completes his
name.
6. The rep’s ID is already filled in, along with the code for the credit card
promotion they’re working on today.
7. Steve fills in the shift information for his rep. He then enters the total
number of applications taken.
8. It looks like from the notes on this sheet that this rep left sick two hours
early. Steve adds a note about this in the system.
9. Time passes as more reps bring in their sheets and Steve completes
entering them in between conversations.
10. After all the sheets are done, Steve looks at a summary screen for the
day. It looks like he’s close to his goal. If the next shift continues at
this rate he’ll beat the plan by 5% or so. That’s good.
11. Steve validates that the base pay is correct at $5 per app, and that
he’s set an individual bonus giving reps $50 each if they reach 20
apps. Next to each rep he sees the calculated pay, base, bonus, and
total pay for the day.
12. The annual sale at Macy’s has brought a lot of people in today. Steve
chooses a “sale increases mall foot traffic” code to add to his shift data
sheet. Frank, his boss, has pestered him to make sure he includes
this type of information in his daily summaries.
Steven
Credit Card Marketing Field
Manager
Steven is a field manager working
at the local shopping center.
He’s in the middle of a long
workday supervising 13 reps
who are busy talking to people
trying to convince them to
apply for a credit card.
40. 40comakers, LLC :: hello@comakewith.us
A narrative imagines the experience of a
product that doesn’t yet exist
UI Storyboard from Margarete Fuss, SAP AG
41. 41comakers, LLC :: hello@comakewith.us
Story map under a story board
Photo courtesy of Carbonite, Boston, MA
41
42. 42comakers, LLC :: hello@comakewith.us
Think:
“mile wide inch deep”
or
“breadth not depth”
You’re trying to get the big
picture
43. 43comakers, LLC :: hello@comakewith.us
Key concepts
Think and write your own definitions in, based on what you
remember
product context
pragmatic persona
measurable product
goal
building the backbone
mile-wide inch-deep
45. 45comakers, LLC :: hello@comakewith.us
Discuss, fill in, refine the
map, and test for
completeness
46. 46comakers, LLC :: hello@comakewith.us
Discussions over story maps help drive
out more details
Repeated review of the story map with
multiple users and subject matter experts will
help test the model for completeness
47. 47
add, rewrite,split,combine,reorganize
add, rewrite,split,combine,reorganize
comakers, LLC :: hello@comakewith.us
Play “wouldn’t it be cool if...”
Look for variations
What else might users of the system have done?
Look for exceptions
What could go wrong, and what would the user have to do to recover?
Consider other users
What might other types of users do to reach their goals?
Add in other product details
48. 48comakers, LLC :: hello@comakewith.us
Key concepts
Stand and stretch. One person will explain a concept while doing a simple
stretch. The rest of the group will copy the stretch.
filling-in through
discussion
variations
exceptions
idea
details
other user types
50. 50comakers, LLC :: hello@comakewith.us
Prioritize stories vertically
then “slice” to small
valuable releases
51. 51comakers, LLC :: hello@comakewith.us
Adding tape lines to the wall lets
participants organize stories into layers
51
52. 52comakers, LLC :: hello@comakewith.us
Maps have latitude and longitude
52
sequence
(time from the user’s perspective)
priority
(time from the
planner and
builder’s
perspective)
53. 53comakers, LLC :: hello@comakewith.us
Planning incremental releases can be a
whole team event
53
54. 54comakers, LLC :: hello@comakewith.us
Releases target business outcomes,
customer, and user segments
* Menlo Innovations organizes personas into a target to help focus releases
55. 55comakers, LLC :: hello@comakewith.us
Use target personas to drive release
strategy
Target a primary persona for a first release
Try a “good-better-best” strategy
56. 56comakers, LLC :: hello@comakewith.us
Minimal Viable Releases target success
for a product with a specific target
audience
MVP: Minimal Viable Product
MMF: Minimal Marketable Feature
To thin a release, first reduce the size of your target market
MVP
1 or more
MMFs
57. 57comakers, LLC :: hello@comakewith.us
You’ll spend most of your time filling in
and validating
58. 58comakers, LLC :: hello@comakewith.us
Key concepts
Pop-up and explain a part of the concept. When finished sit down so that
someone else can pop-up and explain. We’ll count how many we get in 3 minutes.
slicing the map
collaborative planning
MVP & MMF
release strategy
discovery phase
features and story maps
61. 61comakers, LLC :: hello@comakewith.us
Use this simple warm up to show
everyone they already know how to map
Step 1 - Brainstorm: List all the things you did to
get ready to be here today
Starting from the moment you woke up until you
arrived here
Using sticky notes, write the things you did, one
thing per sticky note
62. 62comakers, LLC :: hello@comakewith.us
Play along and quickly list all
the things you did to get
ready this morning...
64. 64comakers, LLC ::
There’s a natural “human size”
for tasks
* Cockburn’s Writing Effective Use Cases
describes goal levels for use cases this way
65. 65comakers, LLC :: hello@comakewith.us
In small groups, organize your stickies into
chronological order - the order things were done - from
left to right
You’ll merge your different timelines into a single
timeline
Stack identical stickies (similar things done at similar
times
Place parts of things under larger things (“wash hair”
might go under “take shower”)
Step 2: Organize
67. 67comakers, LLC :: hello@comakewith.us
People naturally build a
two-dimensional map
67
sub-tasks,
alternatives,
variations, and
details
An imperfect
narrative flow
68. 68comakers, LLC :: hello@comakewith.us
In your same groups, look for groups of stickies that
seem to go together and create a higher-level label for
those
All the stuff done in the bathroom could be called
“bathing” and all the stuff done in the kitchen might be
“getting breakfast.”
You may need to invent some names - what would you
call those things you do to get out of the door?
Gathering laptop, papers, car keys...
Step 3: Find Patterns
70. 70comakers, LLC :: hello@comakewith.us
Look back across the model of the whole experience.
What was your favorite part of the morning, your
high point? Write the high point down on a sticky
with a smiley face. Stick it where you think it goes on
the map.
What part of the morning did you hate? Frustrated
you? Write a note about it with a frowny face. Stick
it where you think it goes on the map.
Step 4: Mark high points and pains
71. 71comakers, LLC :: hello@comakewith.us
Experience maps describe the world
today
71
* Narrative Journey Map
courtesy Duncan Brown of
the Caplin Group
72. 72comakers, LLC :: hello@comakewith.us
Experience maps describe the world
today
72
* Narrative Journey Map
courtesy Duncan Brown of
the Caplin Group
73. 73comakers, LLC :: hello@comakewith.us
The biggest benefit of
modeling this way is not the
data in the model
74. 74comakers, LLC :: hello@comakewith.us
Often when we verbally discuss ideas, we may
incorrectly believe we have the same
understanding
75. 75comakers, LLC :: hello@comakewith.us
Representing our ideas as models allows us
to detect inconsistencies in our
understanding
76. 76comakers, LLC :: hello@comakewith.us
Through discussion and iterative model
building we arrive at a stronger shared
understanding
77. 77comakers, LLC :: hello@comakewith.us
Using that shared understanding we can
work together to arrive at the same
objectives
78. 78comakers, LLC :: hello@comakewith.us
Shared understanding is critical to
successful collaborative work
79. 79comakers, LLC :: hello@comakewith.us
Model collaboratively to
build shared
understanding
80. 80comakers, LLC :: hello@comakewith.us
Key concepts
Write your own definitions in, based on what you remember
user tasks
goal-task-tool
dependency
task goal level
user activity
experience map
journey map
collaborative modeling
81. 81comakers, LLC ::
Now and Later
81
Now and Later photo: Jay Malone via Flickr
http://www.flickr.com/photos/jcorduroy/3725077603/
What challenges do you have
today with user stories?
If you’re not working with
agile development, what
challenges do you have with
project requirements?
What will you change
about what you’re doing
based on what you’ve
heard?
Before we leap, I’d like you to write a now and later card, or sticky, or notebook page.
What’s your situation right now as you’re listening to this?
What’s causing you pain?
Glance at this and think of this as you listen today. Make some notes about anything you hear that could make things better.
Later, at the end of this seminar, I’ll ask you to look back and consider what you’ve heard and imagine a “later” that’s better. You’ll make some notes about what you could do to leverage some of the stuff you’ve heard to make a better later. Because if you can’t leverage it, you’ve wasted your time.... and we’d both hate that.
I’m Jeff Patton
I’m a college art school dropout who went into software development, because for me, programming was easier. Certainly easier than all that hard work it took to be really good at illustration and graphic design.
If you’re a software developer with a bit of an art background, some of you may know that this makes you the UI guy.
My earliest bad memories of software development come from being there when someone first used software I’d poured a lot of hard work into. I remember standing behind someone struggling to figure out my product. I'd been so confident before. I was sure they were going to love it as much as I did.
If any of you can remember being there the first time a product you designed was used, you know what I mean
It was after that experience that I learned that the only way for me to succeed was to not assume I knew my users well,
or assume I was smarter than they were.
I'd have to honestly spend the time to understand them
I'd have to get something in frront of them sooner if I wanted to learn faster. I found I always learned something when I spent time with people that were goiing to use more product.
And after succeeding a few times, I became adicted to creating things that really helped people.
It was after a few years of this when learned what being a UI guy really meant.
In 2000 I first heard of a process called Extreme Programming. They promised to spend lots of face time with customers and users and get small amounts of software in front of people sooner. I thought I’d found a group that valued the same things I did.
But bubble quickly burst for me. I realized that in practice XP meant:
* get a smart person who already knows what to build and call them ‘the customer,’
* ask them exactly what to build,
* build it for them,
* and when they hate it explain to them that that’s the way it’s supposed to work. It’s ‘agile.’
Now don't get me wrong. I really do like agile processes. I like agile ideals. But since my first exprience in 2000 I've been on a rampage... I've been committed add the same level of rigor in decidng what to build that agile processes put into to building. When I add good UX practice and good product thinking to agile - it's exactly the way I want to work.
What you're going to get is a dose of the kinds of thinking and practice I've been championing for the last decade.
In the late 1990s Kent Beck coined the term “Story.” In Extreme Programming Explained stories describe an alternative to working with traditional requirements
The real purpose of what we do in software development is to change the world
<stories aren’t about the solution, they’re about the world with the solution in it>
who, what, and why – they describe the future world.
They’re super hard to write if you can’t imagine the future world.
Many years ago I spoke with a game designer who said “to succeed, you have to be able to play the game in your head.” I thought he was crazy - but I get it now.
Myth: stories have a “right size” for all conversations
Before advancing, look at your list... what part of speech does each item in your list start with? I predict verbs.
In Pruitt and Adlin’s book “The Persona Lifecycle” they describe the creating journey maps. They’re a good example of what I’m talking about.
Journey maps integrate tasks, comments, pain points, questions, and solution ideas.
Duncan Brown from the Caplin group sent me a few photos of their journey maps. They integrate photos from contextual studies and a nifty emotional barometer on the top.
This simple 2D map is a handy structure for visualizing experience, seeing big patterns, and moving from big ideas into little ideas.
Before we leap, I’d like you to write a now and later card, or sticky, or notebook page.
What’s your situation right now as you’re listening to this?
What’s causing you pain?
Glance at this and think of this as you listen today. Make some notes about anything you hear that could make things better.
Later, at the end of this seminar, I’ll ask you to look back and consider what you’ve heard and imagine a “later” that’s better. You’ll make some notes about what you could do to leverage some of the stuff you’ve heard to make a better later. Because if you can’t leverage it, you’ve wasted your time.... and we’d both hate that.