This document discusses effective techniques for slicing user stories into thin slices to facilitate agile development. It begins by introducing the presenter and the purpose of story slicing. It then provides examples of incrementally slicing a story to create a point of sale system, showing how each slice delivers value and reduces risk while building on previous slices. Key techniques discussed include hardcoding values initially instead of building full functionality, using a simple interface, deferring validation and complexity, and starting with zero then one then many related elements. The document encourages applying these techniques in breakout exercises and provides resources for further reading on story splitting patterns.
How Thin is Thin? Effective Story Slicing (Agile DC 2019)Dave Rooney
Most of us have heard the mantra, "Slice your User Stories as thin as possible!" In my travels as a coach since the early 2000's, however, I've rarely seen stories that truly are thin. What are these rare creatures? Why don't I see more of them? Having good User Stories is crucial to the success of teams using them as the means for determining what needs to be built to fulfill a customer's need. Having thinly sliced stories is even more important!
How Thin is Thin - Effective Story Slicing (PrDC Deliver 2019)Dave Rooney
Most of us have heard the mantra, “Slice your User Stories as thin as possible!” In my travels as a coach since the early 2000’s, however, I’ve rarely seen stories that truly are thin. What are these rare creatures? Why don’t I see more of them? Having good User Stories is crucial to the success of teams using them as the means for determining what needs to be built to fulfill a customer’s need. Having thinly sliced stories is even more important!
A deep dive into components of a user story, looking at beyond the basics that we all know (ought to know) and are familiar with. The deck provides guidance on developing individual components that make up a ‘Ready for Dev’ user story.
How to slice user stories, using concepts like low/high fidelity solutions, iterative vs incremental delivery, and hunting for small bits of value rather than breaking down work in technical chunks.
How Thin is Thin? Effective Story Slicing (Agile DC 2019)Dave Rooney
Most of us have heard the mantra, "Slice your User Stories as thin as possible!" In my travels as a coach since the early 2000's, however, I've rarely seen stories that truly are thin. What are these rare creatures? Why don't I see more of them? Having good User Stories is crucial to the success of teams using them as the means for determining what needs to be built to fulfill a customer's need. Having thinly sliced stories is even more important!
How Thin is Thin - Effective Story Slicing (PrDC Deliver 2019)Dave Rooney
Most of us have heard the mantra, “Slice your User Stories as thin as possible!” In my travels as a coach since the early 2000’s, however, I’ve rarely seen stories that truly are thin. What are these rare creatures? Why don’t I see more of them? Having good User Stories is crucial to the success of teams using them as the means for determining what needs to be built to fulfill a customer’s need. Having thinly sliced stories is even more important!
A deep dive into components of a user story, looking at beyond the basics that we all know (ought to know) and are familiar with. The deck provides guidance on developing individual components that make up a ‘Ready for Dev’ user story.
How to slice user stories, using concepts like low/high fidelity solutions, iterative vs incremental delivery, and hunting for small bits of value rather than breaking down work in technical chunks.
Techniques for Effectively Slicing User Stories by Naresh JainNaresh Jain
In order to achieve my goals, as a buyer of your product, I want awesome feature. AT: make sure your users stories don't get in the way.
Users Stories, the tool teams use to break big ideas into small demonstrable deliverable, are easy to describe and challenging to write effectively. In this hands-on workshop you'll learn how to write great user stories and acceptance criteria, that everyone on the team understands. We'll learn various techniques to slice your stories using the tracer-bullet approach. We will discuss what elements should be included in the stories, what criteria you should keep in mind while slicing stories; why the size of your user story is important and how to make them smaller and efficient.
Agenda:
What do you do to Large Stories? Spike, Split, Stub & Timebox (SSST) technique.
Core Slicing Techniques:
1. System Slice
1.a. Static vs. Dynamic
1.b. Real-time vs. Batch Processing
1.c. Build vs. Buy
1.d. Automated vs. Manual Steps
1.e. Defer certain roles
2. Behavioural Slice
2.a. Adjusting Sophistication - MVF (Minimum Viable Feature) or Walking Skeleton
2.a.1. Acceptance Criteria
2.b. By-pass certain steps in the workflow
2.c. Focus on Happy Path First (edge cases later)
2.d. No options - 1 option - Many options
3. Incrementally improve ‘Ilities' (Usability, Scalability, Reliability, etc.)
3.a. Simpler UI (even consider using a standard UI)
3.b. Minmal Data
3.c. Improve Performance Iteratively
Liftoff - how to launch Agile teams and projectsFabio Armani
Liftoff - come lanciare team e progetti Agili
di Fabio Armani
Come per mettere in orbita un razzo è importante effettuare molteplici operazioni preliminare che sono fondamentali per il successo della missione, così per lanciare un progetto o creare un team Agile è fondamentale una fase di 'Liftoff'.
Questo talk, che parte dall'interessantissimo lavoro di Diana Larsen e Ainsley Nies intende combinare le pratiche della fase di Agile Inception portate avanti dall'autore sin dal 2001 con i più moderni principi derivanti da Lean StartUp.
Agile Team Working agreements, also known as team norms, are guidelines developed by the teams as to how they must work together to create a positive, productive process.
What do making cars and writing software have in common?PayPerks
Many components of the Agile system find their roots in lean manufacturing made popular by Toyota in the mid to late 20th century. This talk explains that link, as well as gives an overview of how we use Agile at PayPerks.
Measuring 2.0 - How to handle 100K events/sec - Berlin Buzzwords 2019Niels Basjes
These are the slides of my Berlin Buzzwords 2019 presentation that I gave on 2018 06-17.
This talk is essentially about the choices we made in designing and implementing our streaming system that can do behavioral analytics.
Note that the mentioned Useragent analyzer that is used in this project is an opensources Apache 2.0 licensed project of mine.See https://yauaa.basjes.nl for more information about this tool.
When ordering Matters - Flink Forward EU - Berlin - 2019 Niels Basjes
These are the slides I used for my presentation at the Flink Forward conference in Berlin on 2019-10-09.
https://europe-2019.flink-forward.org/conference-program#when-ordering-matters
Abstract:
In the last decades many systems have been used that were described as "queues" (AQ, ActiveMQ, RabbitMQ, etc.), yet from a computer science perspective these are not queues at all. Many of us have learned to work quite effectively with these messaging systems and we all understand that we cannot expect to receive the messages in any particular order and that we get all messages exactly once (which we can expect with a queue). With the arrival of Kafka and Flink a new class of applications became possible. In this talk I will go into several real applications from the bol.com context that all revolve around low latency behavioral analytics. I will talk about the entire end-to-end pipeline from the webbrowser and application server to application and discuss many of the things to think about when creating your analysis application. I will also touch upon using state machines as a way of doing this type of behavioral analysis using very simple software and show example algorithms from our context.
TALK | Learn how to tap into what your employer sees using Postman + osquery, an open source API for asking questions about devices like laptops, servers, and Docker containers.
Serverless Architectures enable scalable and cost-effective apps to be built faster, so they can dramatically increase the odds of Your Startup's Success!
In "Startups + Serverless = Match made in Heaven" meetup, www.ServerlessToronto.org members discussed how to help Entrepreneurs push their businesses up to "other side of the teeterboard" (without failing) using the Serverless technologies: https://www.youtube.com/watch?v=1SqfJo47kMA
Can Your Mobile Infrastructure Survive 1 Million Concurrent Users?Josiah Renaudin
You’re building the next killer mobile app. How do you ensure that your app is both stable and capable of near-instant data updates? Build a backend! But there’s more to building a backend than standing up a SQL server in your datacenter and calling it a day. Since different types of apps demand different backend services, how do you know what sort of backend you need? And, more importantly, how can you ensure that your backend will scale so you can survive an explosion of users that comes from events like being featured in the app store? Siva Katir and Melissa Benua will discuss the common scenarios facing mobile app developers who are looking to expand beyond just the device and will share best practices learned while building the PlayFab and other companies’ backends. Join Siva and Melissa to learn how you can ensure that your app can scale safely and affordably into the millions of concurrent users (CCU) and across multiple platforms.
The proliferation of good metrics collection and visualization toolkits over the past five years has been a huge benefit to developers. But with so many metrics available, along with a massive proliferation of services and limited cognitive capacity, which ones should we focus on?
Single Source of Truth for Network AutomationAndy Davidson
The importance of building a single source of truth for information within your organisation, when you embark upon a network automation project. Simply automating router configuration steps is not "network automation".
Power to the People: A Stack to Empower Every User to Make Data-Driven DecisionsLooker
Infectious Media runs on data. But, as an ad-tech company that records hundreds of thousands of web events per second, they have have to deal with data at a scale not seen by most companies. You can not make decisions with data when people need to write manual SQL only for queries take 10-20 minutes to return. Infectious Media made the switch to Google BigQuery and Looker and now every member of every team can get the data they need in seconds.
Infectious Media shares:
- Why they chose their current stack
- Why faster data means happier customers
- Advantages and practical implications of storing and processing that much data
Check out the recording at https://info.looker.com/h/i/308848878-power-to-the-people-a-stack-to-empower-every-user-to-make-data-driven-decisions
26 story slicing techniques for any scrum teamagilebin
Why a story needs to be sliced?
Incremental Delivery
Identify valuable ship-able units (VSUs)
Story slicing techniques
Story Naming Convention
Story slicing mistakes
The Future of ETL Isn't What It Used to Beconfluent
Speaker: Gwen Shapira, Principal Data Architect, Confluent
Join Gwen Shapira, Apache Kafka® committer and co-author of ""Kafka: The Definitive Guide,"" as she presents core patterns of modern data engineering and explains how you can use microservices, event streams and a streaming platform like Apache Kafka to build scalable and reliable data pipelines designed to evolve over time.
This is part 1 of 3 in Streaming ETL - The New Data Integration series.
Watch the recording: https://videos.confluent.io/watch/q7roRtNZBnjiT9C3ii88fo?.
Techniques for Effectively Slicing User Stories by Naresh JainNaresh Jain
In order to achieve my goals, as a buyer of your product, I want awesome feature. AT: make sure your users stories don't get in the way.
Users Stories, the tool teams use to break big ideas into small demonstrable deliverable, are easy to describe and challenging to write effectively. In this hands-on workshop you'll learn how to write great user stories and acceptance criteria, that everyone on the team understands. We'll learn various techniques to slice your stories using the tracer-bullet approach. We will discuss what elements should be included in the stories, what criteria you should keep in mind while slicing stories; why the size of your user story is important and how to make them smaller and efficient.
Agenda:
What do you do to Large Stories? Spike, Split, Stub & Timebox (SSST) technique.
Core Slicing Techniques:
1. System Slice
1.a. Static vs. Dynamic
1.b. Real-time vs. Batch Processing
1.c. Build vs. Buy
1.d. Automated vs. Manual Steps
1.e. Defer certain roles
2. Behavioural Slice
2.a. Adjusting Sophistication - MVF (Minimum Viable Feature) or Walking Skeleton
2.a.1. Acceptance Criteria
2.b. By-pass certain steps in the workflow
2.c. Focus on Happy Path First (edge cases later)
2.d. No options - 1 option - Many options
3. Incrementally improve ‘Ilities' (Usability, Scalability, Reliability, etc.)
3.a. Simpler UI (even consider using a standard UI)
3.b. Minmal Data
3.c. Improve Performance Iteratively
Liftoff - how to launch Agile teams and projectsFabio Armani
Liftoff - come lanciare team e progetti Agili
di Fabio Armani
Come per mettere in orbita un razzo è importante effettuare molteplici operazioni preliminare che sono fondamentali per il successo della missione, così per lanciare un progetto o creare un team Agile è fondamentale una fase di 'Liftoff'.
Questo talk, che parte dall'interessantissimo lavoro di Diana Larsen e Ainsley Nies intende combinare le pratiche della fase di Agile Inception portate avanti dall'autore sin dal 2001 con i più moderni principi derivanti da Lean StartUp.
Agile Team Working agreements, also known as team norms, are guidelines developed by the teams as to how they must work together to create a positive, productive process.
What do making cars and writing software have in common?PayPerks
Many components of the Agile system find their roots in lean manufacturing made popular by Toyota in the mid to late 20th century. This talk explains that link, as well as gives an overview of how we use Agile at PayPerks.
Measuring 2.0 - How to handle 100K events/sec - Berlin Buzzwords 2019Niels Basjes
These are the slides of my Berlin Buzzwords 2019 presentation that I gave on 2018 06-17.
This talk is essentially about the choices we made in designing and implementing our streaming system that can do behavioral analytics.
Note that the mentioned Useragent analyzer that is used in this project is an opensources Apache 2.0 licensed project of mine.See https://yauaa.basjes.nl for more information about this tool.
When ordering Matters - Flink Forward EU - Berlin - 2019 Niels Basjes
These are the slides I used for my presentation at the Flink Forward conference in Berlin on 2019-10-09.
https://europe-2019.flink-forward.org/conference-program#when-ordering-matters
Abstract:
In the last decades many systems have been used that were described as "queues" (AQ, ActiveMQ, RabbitMQ, etc.), yet from a computer science perspective these are not queues at all. Many of us have learned to work quite effectively with these messaging systems and we all understand that we cannot expect to receive the messages in any particular order and that we get all messages exactly once (which we can expect with a queue). With the arrival of Kafka and Flink a new class of applications became possible. In this talk I will go into several real applications from the bol.com context that all revolve around low latency behavioral analytics. I will talk about the entire end-to-end pipeline from the webbrowser and application server to application and discuss many of the things to think about when creating your analysis application. I will also touch upon using state machines as a way of doing this type of behavioral analysis using very simple software and show example algorithms from our context.
TALK | Learn how to tap into what your employer sees using Postman + osquery, an open source API for asking questions about devices like laptops, servers, and Docker containers.
Serverless Architectures enable scalable and cost-effective apps to be built faster, so they can dramatically increase the odds of Your Startup's Success!
In "Startups + Serverless = Match made in Heaven" meetup, www.ServerlessToronto.org members discussed how to help Entrepreneurs push their businesses up to "other side of the teeterboard" (without failing) using the Serverless technologies: https://www.youtube.com/watch?v=1SqfJo47kMA
Can Your Mobile Infrastructure Survive 1 Million Concurrent Users?Josiah Renaudin
You’re building the next killer mobile app. How do you ensure that your app is both stable and capable of near-instant data updates? Build a backend! But there’s more to building a backend than standing up a SQL server in your datacenter and calling it a day. Since different types of apps demand different backend services, how do you know what sort of backend you need? And, more importantly, how can you ensure that your backend will scale so you can survive an explosion of users that comes from events like being featured in the app store? Siva Katir and Melissa Benua will discuss the common scenarios facing mobile app developers who are looking to expand beyond just the device and will share best practices learned while building the PlayFab and other companies’ backends. Join Siva and Melissa to learn how you can ensure that your app can scale safely and affordably into the millions of concurrent users (CCU) and across multiple platforms.
The proliferation of good metrics collection and visualization toolkits over the past five years has been a huge benefit to developers. But with so many metrics available, along with a massive proliferation of services and limited cognitive capacity, which ones should we focus on?
Single Source of Truth for Network AutomationAndy Davidson
The importance of building a single source of truth for information within your organisation, when you embark upon a network automation project. Simply automating router configuration steps is not "network automation".
Power to the People: A Stack to Empower Every User to Make Data-Driven DecisionsLooker
Infectious Media runs on data. But, as an ad-tech company that records hundreds of thousands of web events per second, they have have to deal with data at a scale not seen by most companies. You can not make decisions with data when people need to write manual SQL only for queries take 10-20 minutes to return. Infectious Media made the switch to Google BigQuery and Looker and now every member of every team can get the data they need in seconds.
Infectious Media shares:
- Why they chose their current stack
- Why faster data means happier customers
- Advantages and practical implications of storing and processing that much data
Check out the recording at https://info.looker.com/h/i/308848878-power-to-the-people-a-stack-to-empower-every-user-to-make-data-driven-decisions
26 story slicing techniques for any scrum teamagilebin
Why a story needs to be sliced?
Incremental Delivery
Identify valuable ship-able units (VSUs)
Story slicing techniques
Story Naming Convention
Story slicing mistakes
The Future of ETL Isn't What It Used to Beconfluent
Speaker: Gwen Shapira, Principal Data Architect, Confluent
Join Gwen Shapira, Apache Kafka® committer and co-author of ""Kafka: The Definitive Guide,"" as she presents core patterns of modern data engineering and explains how you can use microservices, event streams and a streaming platform like Apache Kafka to build scalable and reliable data pipelines designed to evolve over time.
This is part 1 of 3 in Streaming ETL - The New Data Integration series.
Watch the recording: https://videos.confluent.io/watch/q7roRtNZBnjiT9C3ii88fo?.
Learnings from 7 Years of Integrating Mission-Critical IBM Z® and IBM i with ...Precisely
Mainframe (z/OS®) & IBM i systems are incredibly important for many businesses but are often outside the holistic IT Operations Analytics (ITOA) observability available in Splunk. Exclude them & you will miss valuable, critical insights. Ironstream delivers valuable log data, events and intelligence from both IBM mainframe and IBM i environments into Splunk, providing a true 360-degree view of your IT infrastructure.
This session will examine how adding more agility; faster MTTI/MTTR; deeper visibility & increased efficiencies address problems seen by real-world customers over the last 7 years. Effectively addressing these problems has resulted in millions of dollars of cost-savings.
See how you can use Precisely Ironstream to:
- Tap into mainframe and IBM i machine data the easy way!
- Get machine data into your Cloud, On-Prem, ITSI, Enterprise Security, or AIOps environments
- Address the high-value use cases
- Realize fast ROI & be ready for the future!
Sencha Auckland Conference (SenchaCon) AdvanceRetail PresentationAndrew Bell
Retail Technology Trends & Embracing Change as an ISV discusses some of the emerging trends in the field of retail technology and showcases how AdvanceRetail Technology Ltd has evolved from using pure Microsoft based technology solutions to embracing a heterogeneous technology solution stack that includes HTML5 JavaScript frameworks from Sencha
This is the presentation of the online shopping management system. I created this into Canva application. I created this for my college project presentation. This project have all the details related to the online shopping management system. I try to put best of my knowledge to provide the best presentation. The project have all the info like , introduction, Problem Statement, Scope and features, objectives and goals , data dictionary, context level diagram, Data flow diagram, ER diagram, report, conclusion, future scope, bibliography etc. This is totally imaginary project this do not contain any copyrights.
Similar to How Thin is Thin? Effective User Story Slicing (20)
#NoBigProcesses - Getting More Done by Doing Less (PrDC Deliver 2019)Dave Rooney
You may have heard about the #NoEstimates movement, and even #NoProjects. Both of those are keen to examine the assumptions behind two key aspects of delivering software. But what about the process itself? Do we even need approaches like Scrum, Kanban, SAFe, or Extreme Programming in order to be successful? Is following a pre-defined process helpful at all? Is there a simpler way to be effective?
#NoProcesses - Doing More by Doing LessDave Rooney
You may have heard about the #NoEstimates movement, and even #NoProjects. Both of those are keen to examine the assumptions behind two key aspects of delivering software. But what about the process itself? Do we even need approaches like Scrum, Kanban, SAFe, or Extreme Programming in order to be successful? Is following a pre-defined process helpful at all? Is there a simpler way to be effective?
This session starts with two key principles common to all successful software delivery approaches and builds out from there based on the experience of the participants. Like #NoEstimates and #NoProjects, the name doesn’t really mean to eliminate process altogether, but rather to build a process that works for your team in your business domain with your technology stack.
When the Phoenix Pay system was released in April 2016, it had severe problems affecting some 70% of the people who the system was intended to pay. It has been fraught with issues ever since resulting in under and overpayments of those employees, and in some cases no payments at all. Hundreds of millions of dollars have been and will be spent to correct the pay issues and update the system. This was yet another example of the ineffectiveness of the antiquated approach that the government used to deliver Phoenix.
When the 2018 budget was tabled, nearly half a BILLION dollars was allocated to fixing Phoenix! What seemed like a footnote to that was $16 million over two years to study how to build the replacement system.
Study. That's what finally broke me. I had been grumbling at the stories of Phoenix for years, but this finally triggered me to do something.
From the Ashes of Phoenix - PrDeliver 2018Dave Rooney
When the Phoenix Pay system was released in April 2016, it had severe problems affecting some 70% of the people who the system was intended to pay. It has been fraught with issues ever since resulting in under and overpayments of those employees, and in some cases no payments at all. Hundreds of millions of dollars have been and will be spent to correct the pay issues and update the system. This was yet another example of the ineffectiveness of the antiquated approach that the government used to deliver Phoenix.
When the 2018 budget was tabled, nearly half a BILLION dollars was allocated to fixing Phoenix! What seemed like a footnote to that was $16 million over two years to study how to build the replacement system.
Study. That's what finally broke me. I had been grumbling at the stories of Phoenix for years, but this finally triggered me to do something.
(Slides and Notes from Agile 2010)
Vehicular traffic, grocery store lines, and even making dinner in your kitchen all need require Flow in order to work effectively. In software projects Flow is equally important and the same dire consequences result when disruption occurs. The fact is that Flow is a core concept behind all Agile approaches, and needs to be maximized at several levels.
Understanding Globus Data Transfers with NetSageGlobus
NetSage is an open privacy-aware network measurement, analysis, and visualization service designed to help end-users visualize and reason about large data transfers. NetSage traditionally has used a combination of passive measurements, including SNMP and flow data, as well as active measurements, mainly perfSONAR, to provide longitudinal network performance data visualization. It has been deployed by dozens of networks world wide, and is supported domestically by the Engagement and Performance Operations Center (EPOC), NSF #2328479. We have recently expanded the NetSage data sources to include logs for Globus data transfers, following the same privacy-preserving approach as for Flow data. Using the logs for the Texas Advanced Computing Center (TACC) as an example, this talk will walk through several different example use cases that NetSage can answer, including: Who is using Globus to share data with my institution, and what kind of performance are they able to achieve? How many transfers has Globus supported for us? Which sites are we sharing the most data with, and how is that changing over time? How is my site using Globus to move data internally, and what kind of performance do we see for those transfers? What percentage of data transfers at my institution used Globus, and how did the overall data transfer performance compare to the Globus users?
Listen to the keynote address and hear about the latest developments from Rachana Ananthakrishnan and Ian Foster who review the updates to the Globus Platform and Service, and the relevance of Globus to the scientific community as an automation platform to accelerate scientific discovery.
How Recreation Management Software Can Streamline Your Operations.pptxwottaspaceseo
Recreation management software streamlines operations by automating key tasks such as scheduling, registration, and payment processing, reducing manual workload and errors. It provides centralized management of facilities, classes, and events, ensuring efficient resource allocation and facility usage. The software offers user-friendly online portals for easy access to bookings and program information, enhancing customer experience. Real-time reporting and data analytics deliver insights into attendance and preferences, aiding in strategic decision-making. Additionally, effective communication tools keep participants and staff informed with timely updates. Overall, recreation management software enhances efficiency, improves service delivery, and boosts customer satisfaction.
OpenMetadata Community Meeting - 5th June 2024OpenMetadata
The OpenMetadata Community Meeting was held on June 5th, 2024. In this meeting, we discussed about the data quality capabilities that are integrated with the Incident Manager, providing a complete solution to handle your data observability needs. Watch the end-to-end demo of the data quality features.
* How to run your own data quality framework
* What is the performance impact of running data quality frameworks
* How to run the test cases in your own ETL pipelines
* How the Incident Manager is integrated
* Get notified with alerts when test cases fail
Watch the meeting recording here - https://www.youtube.com/watch?v=UbNOje0kf6E
AI Pilot Review: The World’s First Virtual Assistant Marketing SuiteGoogle
AI Pilot Review: The World’s First Virtual Assistant Marketing Suite
👉👉 Click Here To Get More Info 👇👇
https://sumonreview.com/ai-pilot-review/
AI Pilot Review: Key Features
✅Deploy AI expert bots in Any Niche With Just A Click
✅With one keyword, generate complete funnels, websites, landing pages, and more.
✅More than 85 AI features are included in the AI pilot.
✅No setup or configuration; use your voice (like Siri) to do whatever you want.
✅You Can Use AI Pilot To Create your version of AI Pilot And Charge People For It…
✅ZERO Manual Work With AI Pilot. Never write, Design, Or Code Again.
✅ZERO Limits On Features Or Usages
✅Use Our AI-powered Traffic To Get Hundreds Of Customers
✅No Complicated Setup: Get Up And Running In 2 Minutes
✅99.99% Up-Time Guaranteed
✅30 Days Money-Back Guarantee
✅ZERO Upfront Cost
See My Other Reviews Article:
(1) TubeTrivia AI Review: https://sumonreview.com/tubetrivia-ai-review
(2) SocioWave Review: https://sumonreview.com/sociowave-review
(3) AI Partner & Profit Review: https://sumonreview.com/ai-partner-profit-review
(4) AI Ebook Suite Review: https://sumonreview.com/ai-ebook-suite-review
Gamify Your Mind; The Secret Sauce to Delivering Success, Continuously Improv...Shahin Sheidaei
Games are powerful teaching tools, fostering hands-on engagement and fun. But they require careful consideration to succeed. Join me to explore factors in running and selecting games, ensuring they serve as effective teaching tools. Learn to maintain focus on learning objectives while playing, and how to measure the ROI of gaming in education. Discover strategies for pitching gaming to leadership. This session offers insights, tips, and examples for coaches, team leads, and enterprise leaders seeking to teach from simple to complex concepts.
A Study of Variable-Role-based Feature Enrichment in Neural Models of CodeAftab Hussain
Understanding variable roles in code has been found to be helpful by students
in learning programming -- could variable roles help deep neural models in
performing coding tasks? We do an exploratory study.
- These are slides of the talk given at InteNSE'23: The 1st International Workshop on Interpretability and Robustness in Neural Software Engineering, co-located with the 45th International Conference on Software Engineering, ICSE 2023, Melbourne Australia
How to Position Your Globus Data Portal for Success Ten Good PracticesGlobus
Science gateways allow science and engineering communities to access shared data, software, computing services, and instruments. Science gateways have gained a lot of traction in the last twenty years, as evidenced by projects such as the Science Gateways Community Institute (SGCI) and the Center of Excellence on Science Gateways (SGX3) in the US, The Australian Research Data Commons (ARDC) and its platforms in Australia, and the projects around Virtual Research Environments in Europe. A few mature frameworks have evolved with their different strengths and foci and have been taken up by a larger community such as the Globus Data Portal, Hubzero, Tapis, and Galaxy. However, even when gateways are built on successful frameworks, they continue to face the challenges of ongoing maintenance costs and how to meet the ever-expanding needs of the community they serve with enhanced features. It is not uncommon that gateways with compelling use cases are nonetheless unable to get past the prototype phase and become a full production service, or if they do, they don't survive more than a couple of years. While there is no guaranteed pathway to success, it seems likely that for any gateway there is a need for a strong community and/or solid funding streams to create and sustain its success. With over twenty years of examples to draw from, this presentation goes into detail for ten factors common to successful and enduring gateways that effectively serve as best practices for any new or developing gateway.
Climate Science Flows: Enabling Petabyte-Scale Climate Analysis with the Eart...Globus
The Earth System Grid Federation (ESGF) is a global network of data servers that archives and distributes the planet’s largest collection of Earth system model output for thousands of climate and environmental scientists worldwide. Many of these petabyte-scale data archives are located in proximity to large high-performance computing (HPC) or cloud computing resources, but the primary workflow for data users consists of transferring data, and applying computations on a different system. As a part of the ESGF 2.0 US project (funded by the United States Department of Energy Office of Science), we developed pre-defined data workflows, which can be run on-demand, capable of applying many data reduction and data analysis to the large ESGF data archives, transferring only the resultant analysis (ex. visualizations, smaller data files). In this talk, we will showcase a few of these workflows, highlighting how Globus Flows can be used for petabyte-scale climate analysis.
In 2015, I used to write extensions for Joomla, WordPress, phpBB3, etc and I ...Juraj Vysvader
In 2015, I used to write extensions for Joomla, WordPress, phpBB3, etc and I didn't get rich from it but it did have 63K downloads (powered possible tens of thousands of websites).
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.
Essentials of Automations: The Art of Triggers and Actions in FMESafe Software
In this second installment of our Essentials of Automations webinar series, we’ll explore the landscape of triggers and actions, guiding you through the nuances of authoring and adapting workspaces for seamless automations. Gain an understanding of the full spectrum of triggers and actions available in FME, empowering you to enhance your workspaces for efficient automation.
We’ll kick things off by showcasing the most commonly used event-based triggers, introducing you to various automation workflows like manual triggers, schedules, directory watchers, and more. Plus, see how these elements play out in real scenarios.
Whether you’re tweaking your current setup or building from the ground up, this session will arm you with the tools and insights needed to transform your FME usage into a powerhouse of productivity. Join us to discover effective strategies that simplify complex processes, enhancing your productivity and transforming your data management practices with FME. Let’s turn complexity into clarity and make your workspaces work wonders!
Large Language Models and the End of ProgrammingMatt Welsh
Talk by Matt Welsh at Craft Conference 2024 on the impact that Large Language Models will have on the future of software development. In this talk, I discuss the ways in which LLMs will impact the software industry, from replacing human software developers with AI, to replacing conventional software with models that perform reasoning, computation, and problem-solving.
Introducing Crescat - Event Management Software for Venues, Festivals and Eve...Crescat
Crescat is industry-trusted event management software, built by event professionals for event professionals. Founded in 2017, we have three key products tailored for the live event industry.
Crescat Event for concert promoters and event agencies. Crescat Venue for music venues, conference centers, wedding venues, concert halls and more. And Crescat Festival for festivals, conferences and complex events.
With a wide range of popular features such as event scheduling, shift management, volunteer and crew coordination, artist booking and much more, Crescat is designed for customisation and ease-of-use.
Over 125,000 events have been planned in Crescat and with hundreds of customers of all shapes and sizes, from boutique event agencies through to international concert promoters, Crescat is rigged for success. What's more, we highly value feedback from our users and we are constantly improving our software with updates, new features and improvements.
If you plan events, run a venue or produce festivals and you're looking for ways to make your life easier, then we have a solution for you. Try our software for free or schedule a no-obligation demo with one of our product specialists today at crescat.io
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
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.
First Steps with Globus Compute Multi-User Endpoints
How Thin is Thin? Effective User Story Slicing
1. How Thin is Thin?
Effective Story Slicing
Gatineau-Ottawa Agile Tour
November 21, 2016
1
2. How Thin is Thin? Effective Story Slicing
Who is this guy?
2
•Software Development Manager
at You.i TV
•Recovering Developer & Agilist,
but frequently falls off the wagon
•Coding since C wasn’t even a
teenager yet and Java was
something you drank
•Part of the Agile community for
this entire century
3. How Thin is Thin? Effective Story Slicing
But enough about me! Who are you?
3
• Product Managers?
• Product Owners?
• Business Analysts?
• ScrumMasters?
• Developers?
• QA?
• UX?
• Architects?
• Management?
• ???
4. How Thin is Thin? Effective Story Slicing
4
Why Use Small Stories?
• Better flow
• Better focus
• Reduced risk
• Improved visibility
5. How Thin is Thin? Effective Story Slicing
5
Why Small?
6. How Thin is Thin? Effective Story Slicing
6
So What Does Thin Mean?
User Interface
Web Server
Application Server
Business Logic
Database
Story
• A single “slice” through all layers of a
system
• Just enough functionality to provide
value to the Product Owner
• The Team can easily identify what has
to be done to deliver the story
7. How Thin is Thin? Effective Story Slicing
7
DatabaseRemote API
What About non-Web Systems? There’s no difference!
User Interface
Business Logic
Database
Story
User Interface
Business Logic
Story
API Gateway
Business Logic
Story
8. How Thin is Thin? Effective Story Slicing
8
A “Real World” Example - The Point of Sale (POS) System
•Client was building a web-based POS
system for salespeople taking orders in
the field
•The orders would be stored in the POS
database, but they would also be sent to
the Oracle back-end eBusiness Suite
•Customer and Product data would come
from the Oracle eBusiness Suite
9. How Thin is Thin? Effective Story Slicing
9
The First Story
• Used Personas and Story Mapping to identify how
the system would support the work of the
salespeople
• The Product Owner determined that the most
fundamental aspect of the system was to create
orders
10. How Thin is Thin? Effective Story Slicing
10
The First Story
TOO BIG!
• Used Personas and Story Mapping to identify how
the system would support the work of the
salespeople
• The Product Owner determined that the most
fundamental aspect of the system was to create
orders
12. How Thin is Thin? Effective Story Slicing
12
For the first Story...
13. How Thin is Thin? Effective Story Slicing
13
For the first Story...
• Didn’t create tables for the Customer or
Product
• Used hard-coded values for both
• No validation of those values
• Simple web page with “Create Order” button
• Second page to show that the order was
created (could have even been validated with
an SQL query!)
14. How Thin is Thin? Effective Story Slicing
14
Was This Story “Thin”?
User Interface
Web Server
Application Server
Business Logic
Database
Story
• A single “slice” through all layers of a
system
• Required work in all layers and created
the foundation for all later stories
• Just enough functionality to provide value
to the Product Owner
• An Order was created
• The Team can easily identify what has to be
done to deliver the story
• Very small, easily verified
15. How Thin is Thin? Effective Story Slicing
15
The Next Story...
16. How Thin is Thin? Effective Story Slicing
16
The Next Story...
• Still using a hard-coded value for the Product
• Customer ID is entered manually
• Still no validation of those values
• Web page now has a text field for the
Customer ID as well as“Create Order” button
• Second page to show that the order was
created (could have even been validated with
an SQL query!)
17. How Thin is Thin? Effective Story Slicing
17
Still “Thin”?
User Interface
Web Server
Application Server
Business Logic
Database
Story
• A single “slice” through all layers of a
system
• Just enough functionality to provide value
to the Product Owner
• An Order was created with the
specified Customer ID
• The Team can easily identify what has to be
done to deliver the story
• Very small, easily verified
18. How Thin is Thin? Effective Story Slicing
18
The Next Next Story...
19. How Thin is Thin? Effective Story Slicing
19
The Next Next Story...
• Still using a hard-coded value for the Product
• Customer is selected from a list of valid customers,
but hard-coded into the page
• No validation of the product, but the customer will be
valid
• Web page now has a drop-down list for the Customer
as well as the “Create Order” button
• Second page to show that the order was created
(could have even been validated with an SQL query!)
20. How Thin is Thin? Effective Story Slicing
20
Are we still “Thin”?
User Interface
Web Server
Application Server
Business Logic
Database
Story
• A single “slice” through all layers of a
system
• Just enough functionality to provide value
to the Product Owner
• An Order was created with the
selected Customer ID
• The Team can easily identify what has to be
done to deliver the story
• Very small, easily verified
21. How Thin is Thin? Effective Story Slicing
21
The Stories Continue...
22. How Thin is Thin? Effective Story Slicing
22
The Stories Continue...
• The Product ID is entered in a text field
• Customer is selected from a list of valid customers,
but hard-coded into the page
• No validation of the product, but the customer will be
valid
• Web page now has a drop-down list for the
Customer, a text field for the Product and a “Create
Order” button
• Second page to show that the order was created
23. How Thin is Thin? Effective Story Slicing
23
Are we still “Thin”?
User Interface
Web Server
Application Server
Business Logic
Database
Story
• A single “slice” through all layers of a
system
• Required work in all layers and created
the foundation for all later stories
• Just enough functionality to provide value
to the Product Owner
• An Order was created with the
selected Customer ID and a Line Item
was added for the Product ID entered
• The Team can easily identify what has to be
done to deliver the story
• Very small, easily verified
24. How Thin is Thin? Effective Story Slicing
24
Let’s Skip Ahead A Bit…
25. How Thin is Thin? Effective Story Slicing
25
Let’s Skip Ahead A Bit…
• We can now enter multiple Products selected from a
list, hard-coded into the page
• Customer is selected from a list of valid customers,
but hard-coded into the page
• Both the product and customer will be valid
• Web page now has a drop-down list for the
Customer, multiple drop-down lists for the Products
and a “Create Order” button
• Second page to show that the order was created
26. How Thin is Thin? Effective Story Slicing
26
Are we still “Thin”?
User Interface
Web Server
Application Server
Business Logic
Database
Story
• A single “slice” through all layers of a
system
• Required work in all layers and created
the foundation for all later stories
• Just enough functionality to provide value
to the Product Owner
• An Order was created with the
selected Customer ID and Line Items
were created for each of the Products
• The Team can easily identify what has to be
done to deliver the story
• Very small, easily verified
27. How Thin is Thin? Effective Story Slicing
27
Ahead even further…
28. How Thin is Thin? Effective Story Slicing
28
Ahead even further…
• Both stories use the back-end Product and Customer
services to fill the drop-down lists
• The lists are valid as of the time the page is rendered
since they’re using the most up to date data
• The page is now a classic master/detail view with line
items for the products
29. How Thin is Thin? Effective Story Slicing
29
Are we still “Thin”?
User Interface
Web Server
Application Server
Business Logic
Database
Story
• A single “slice” through all layers of a
system
• Just enough functionality to provide value
to the Product Owner
• An Order was created using valid
Customers and Products from the
back-end services
• The Team can easily identify what has to be
done to deliver the story
• Very small, easily verified
30. How Thin is Thin? Effective Story Slicing
30
All of that from One Story!
• We built out Create Order using many small, valuable
slices
• Each one delivered value
• Each one further reduced risk
• Each one was tested:
• JUnit microtests at the code level
• Cucumber scenarios at the story level
• Each one allowed incremental delivery of the system
architecture
31. How Thin is Thin? Effective Story Slicing
So what did we just see?
• We used hard-coded values to simplify by excluding any
processing of user data entry
• A simple UI was used that was barely sufficient to support the
stories
• No validation of data entered before it was really required
• A story that had no “child” records was followed by a story with
one child then a story with many children
• Although the final system would have an interface with the
Oracle back-end services, we deferred using that interface until
it was necessary
31
32. How Thin is Thin? Effective Story Slicing
32
Story Splitting Patterns
• Hard coding values;
• Simple interface;
• Defer validation;
• Zero, then One, then Many (with the Products);
• Defer complexity (with the back-end Services).
33. How Thin is Thin? Effective Story Slicing
Exercise: The Digital Personal Video Recorder (PVR)
33
•Process:
•Break out into groups of 6-10 (e.g. your table)
•Don’t worry about hardware details, focus on the stories about
someone will use the PVR
•Brainstorm the high-level functionality that should exist
•Brainstorm the stories that will deliver that functionality iteratively and
incrementally
34. How Thin is Thin? Effective Story Slicing
• The system downloads program information over Ethernet.
• The user can configure the following:
• Maximum number of episodes to record
• Finding the same show on other channels
• Time to keep the episodes before automatically deleting them
• Record only new or new and repeat episodes
• Shows can be rated when watched. This information is anonymously fed to an online
service that tracks ratings.
• The system makes recommendations based on what you like compared to what other
people like (all anonymously).
• The system integrates with social media like FaceBook, Twitter, etc.
Exercise: The Digital Personal Video Recorder (PVR)
34
35. How Thin is Thin? Effective Story Slicing
Resources & Further Reading
• Story Splitting Patterns
• User Stories - An Agile Introduction
• How to Enable Estimate-Free Development
• It’s Just a Feature-for-Feature Port
35
• Questions about the session? Contact me at dave@daverooney.ca
• Interested in changing the world of video? We’re hiring at You.i TV!