The document discusses the potential shortcomings of relying solely on user stories in agile development. It introduces the concept of "active architecture" as a way to address these shortcomings by minimizing rework, ensuring consistency across iterations, and identifying potential gaps in the design. The document suggests active architecture can help complement user stories and planning poker sessions.
Sdec11 when user stories are not enoughTerry Bunio
This document discusses the concept of "active architecture" as a way to address potential shortcomings of user stories in agile development. It provides examples of how active architecture uses component conversations and technical tasks to help ensure design consistency and completeness across iterations. The document advocates for using active architecture to envision solutions at a high level through lightweight documentation and design diagrams in order to minimize rework and catch any missing requirements or design gaps earlier.
Microservices are all the rage. They are the silver bullet of architectural styles. But what does it take to implement them and make them work? What are the foundations to build using this architectural style. In this session, you will learn about microservices from a pragmatic standpoint, based on about 2 years of experience in consulting on the architectural style. Rather than look at the purist approach, as outlined by Martin Fowler, and others, you will learn what works and what doesn't, based on experience in the field. Session includes:
* Foundational topics necessary to implement microservices
* Basics on the architectural style as they apply to real world problems
* Necessary It and shifts to implement microservices in the Enterprise
This document discusses Lean UX techniques that can be applied at different stages of product development. It begins with an overview of the goals of learning about Lean UX techniques and practicing collaborative design. Various techniques are then mapped to different development stages. Meeting participants are asked to suggest additional techniques and vote on ones they want to learn more about. Selected techniques are then briefly described, including contextual inquiry, stakeholder mapping, user experience mapping, personas, empathy mapping, elevator pitches, inception decks, user stories, story mapping, journey maps, and storyboards.
Lean UX presented by Fabio Armani at the Bettersoftware 2012 Conference in september 2012.
Cosa è Lean UX?
User Centered Design x Lean Startup (Customer Development + approcci Lean & Agile).
Per la prima volta, i metodi User Centered Design hanno il dovuto slancio nel mondo degli affari.
Quando la comunità imprenditoriale comincia a misurare il valore dell'esperienza dell'utente, è il momento in cui essa investe su questo importante aspetto come un driver di valore, piuttosto che come un costo da minimizzare.
Quando la scienza del Lean Startup include lo "user centered design" come uno dei suoi attrattori principali, noi progettisti abbiamo una nuova opportunità di fare grandi cose.
In questo talk vorrei parlare dell'importanza del movimento Lean UX e di come questo possa condurre alla realizzazione di un team integrato che superi il semplice concetto di Product Owner, andando a definire un più vasto concetto di Product Ownership.
Oltre alla trattazione teorica dei concetti fondamentali, verranno forniti esempi tratti dalle mie molteplici esperienze di Coaching e Consulting in diversi contesti con aziende di medie e grandi dimensioni.
This document discusses the path of Trish Rempel and Brent Hamm's team at Friesens Corporation towards adopting agile practices. It outlines their current strengths and issues, as well as barriers to adopting agile. Their first steps included establishing improvement goals and training. The document contrasts traditional "waterfall" approaches like delivering late and solo work with agile practices like iterative delivery, examples-based specifications, team development, and limiting work-in-progress. It advises that agile is more about attitudes than processes and emphasizes improvement, learning, collaboration and having someone keep agile momentum.
The document discusses 7 ways to make an app learnable, usable, and enjoyable for users. It covers topics like integrating business goals, customer goals, prioritizing goals, recognizing good user experience, and adopting a customer-centric UX philosophy. The presentation aims to provide strategies for designing successful apps.
Sdec11 when user stories are not enoughTerry Bunio
This document discusses the concept of "active architecture" as a way to address potential shortcomings of user stories in agile development. It provides examples of how active architecture uses component conversations and technical tasks to help ensure design consistency and completeness across iterations. The document advocates for using active architecture to envision solutions at a high level through lightweight documentation and design diagrams in order to minimize rework and catch any missing requirements or design gaps earlier.
Microservices are all the rage. They are the silver bullet of architectural styles. But what does it take to implement them and make them work? What are the foundations to build using this architectural style. In this session, you will learn about microservices from a pragmatic standpoint, based on about 2 years of experience in consulting on the architectural style. Rather than look at the purist approach, as outlined by Martin Fowler, and others, you will learn what works and what doesn't, based on experience in the field. Session includes:
* Foundational topics necessary to implement microservices
* Basics on the architectural style as they apply to real world problems
* Necessary It and shifts to implement microservices in the Enterprise
This document discusses Lean UX techniques that can be applied at different stages of product development. It begins with an overview of the goals of learning about Lean UX techniques and practicing collaborative design. Various techniques are then mapped to different development stages. Meeting participants are asked to suggest additional techniques and vote on ones they want to learn more about. Selected techniques are then briefly described, including contextual inquiry, stakeholder mapping, user experience mapping, personas, empathy mapping, elevator pitches, inception decks, user stories, story mapping, journey maps, and storyboards.
Lean UX presented by Fabio Armani at the Bettersoftware 2012 Conference in september 2012.
Cosa è Lean UX?
User Centered Design x Lean Startup (Customer Development + approcci Lean & Agile).
Per la prima volta, i metodi User Centered Design hanno il dovuto slancio nel mondo degli affari.
Quando la comunità imprenditoriale comincia a misurare il valore dell'esperienza dell'utente, è il momento in cui essa investe su questo importante aspetto come un driver di valore, piuttosto che come un costo da minimizzare.
Quando la scienza del Lean Startup include lo "user centered design" come uno dei suoi attrattori principali, noi progettisti abbiamo una nuova opportunità di fare grandi cose.
In questo talk vorrei parlare dell'importanza del movimento Lean UX e di come questo possa condurre alla realizzazione di un team integrato che superi il semplice concetto di Product Owner, andando a definire un più vasto concetto di Product Ownership.
Oltre alla trattazione teorica dei concetti fondamentali, verranno forniti esempi tratti dalle mie molteplici esperienze di Coaching e Consulting in diversi contesti con aziende di medie e grandi dimensioni.
This document discusses the path of Trish Rempel and Brent Hamm's team at Friesens Corporation towards adopting agile practices. It outlines their current strengths and issues, as well as barriers to adopting agile. Their first steps included establishing improvement goals and training. The document contrasts traditional "waterfall" approaches like delivering late and solo work with agile practices like iterative delivery, examples-based specifications, team development, and limiting work-in-progress. It advises that agile is more about attitudes than processes and emphasizes improvement, learning, collaboration and having someone keep agile momentum.
The document discusses 7 ways to make an app learnable, usable, and enjoyable for users. It covers topics like integrating business goals, customer goals, prioritizing goals, recognizing good user experience, and adopting a customer-centric UX philosophy. The presentation aims to provide strategies for designing successful apps.
The Agile Drupalist - Methodologies & Techniques for Running Effective Drupal...Adrian Jones
More and more clients are asking for Agile development for their projects, in particular the Scrum methodology, but do they really know what they are getting into? Both Waterfall and Scrum are viable methodologies, but each is best suited to particular situations, clients, and projects - neither can be considered the better methodology in all circumstances.
This presentation discusses the potential advantages of using Agile development for building sites in Drupal, but also the potential road-bumps and pitfalls.
The document discusses agile analysis and the role of the agile analyst. It describes common misconceptions about agile analysis and introduces techniques for effective agile analysis, including defining objectives, understanding the business domain through personas and goals, identifying requirements through user stories, scenarios, and story trees, and clarifying requirements through prototyping. The role of the agile analyst is described as a customer advocate, agile coach, facilitator, tester, and story librarian.
Exploring ux practices 4 product development agile2012drewz lin
This document describes a workshop on exploring Lean UX techniques and when they should be applied. [1] The goals of the workshop are to learn about Lean UX techniques that can be used at different development stages and do a collaborative design session to develop a minimum viable product (MVP) mobile app. [2] The workshop involves reviewing development stages and commonly used Lean UX techniques, brainstorming additional techniques, and doing a collaborative design exercise where teams research, scope, prototype, test and pitch a mobile networking app for conference attendees. [3] A retrospective is held at the end to discuss lessons learned.
The document discusses achieving better requirements on Agile projects. It begins by introducing traditional structured requirements approaches and how Agile differs. The main points covered include:
- User stories are the basis for requirements on Agile projects, bridging business goals to implementation. Stories should fit in iterations.
- Common pitfalls when dealing with Agile requirements include lack of context, unclear acceptance criteria, and not accounting for all work.
- The document recommends adopting seven habits to improve requirements, such as establishing scope and context, prioritizing based on business value, and elaborating requirements progressively with just enough detail. Acceptance tests should define requirements.
Presentation from Agile Base Camp 2 conference (Kiev, may 2010) about major activities to do before starting iterative development with one of the Agile methodologies.
Agile estimation and planning focuses on iterative development with short planning cycles. Teams work together in short iterations to deliver working software. Planning occurs through story mapping and estimation rather than detailed Gantt charts. Constant inspection and adaptation allows teams to respond to changes rather than rigidly following a predefined plan. Traditional waterfall planning fails because it relies on overly optimistic estimates far into the future and does not adapt to new information learned.
Designing an MVP that works for users (2 and 1/2 hours) @Lean UX NYC 2013Ariadna Font Llitjos
2 and 1/2 hour workshop that covers contextual inquiry, empathy map, user experience map, MVP, elevator pitch, flow diagrams, stories, paper prototype and guerrilla usability testing.
This document discusses user story mapping, an agile technique for planning and prioritizing product development work. It provides definitions of key terms like user activities, user tasks, and user stories. It also outlines the basic steps to do user story mapping, such as gathering user tasks, grouping and ordering them, adding more detailed stories, and prioritizing and breaking work into releases. The document notes that while agile aims to be simple, it is not always easy to implement due to competing interests. It suggests user story mapping can help with decision making, delivering value, and addressing scepticism.
This document discusses applying lean and agile principles to SharePoint development. It introduces lean concepts like Kanban and agile frameworks like Scrum and XP. It emphasizes techniques like automated testing, test-driven development (TDD), and continuous integration. The document acknowledges challenges in applying these techniques to SharePoint but provides examples of how to address them through practices like unit testing with isolation frameworks and continuous integration with PowerShell scripts.
Introduction to the Kanban as applied to software development. Delivered in Kirkland, WA in Nov 2011 by Dynacron Group.
Dynacron Group is an Agile software technology consulting firm. We provide training, consulting, and hands-on implementation for software projects in the Pacific Northwest.
User centric design focuses on optimizing the user interface around how users work rather than forcing users to change how they work. The presentation discusses adopting a user centric approach through:
1) Understanding user behavior and tasks rather than what developers wish users would do.
2) Integrating usability into all stages of design, development, and testing so all teams understand users.
3) Validating new development matches design through usability testing to prevent major defects in the final release.
This document provides 10 tips for software architects. It begins by introducing the author and their background. It then discusses that the role of a software architect is not well-defined and involves managing non-functional requirements and quality. Architects are responsible for defining and enforcing architecture. The document discusses how architects fit into agile development methodologies like Scrum. It argues that "architect" may not be the best metaphor and discusses an alternative view of architects as master craftsmen. The tips emphasize having your own opinion, improving vocabulary, eating your own dog food, avoiding broken windows, using domain-driven design strategically, caring about code and architecture, measuring and reducing complexity, and managing dependencies.
This document discusses various types of architecture including enterprise, solution, integration, software, business, and domain architecture. It also outlines key architecture principles and deliverables. The principles include target architecture, roadmap, view models, patterns used in the solution, peer review, and governance. Key deliverables include documentation of these principles, various views of the system, and references. Maintaining architecture is important to enable the solution, ease implementation through patterns and alignment, and support the system post-deployment through quality attributes.
ALE 2012 session description: In this highly collaborative workshop, we will apply a couple of UX practices and techniques, such as empathy maps, stakeholder maps, storyboards, sketchboards and paper prototype usability testing that will allow teams to focus on quick validation and delivery of killer apps that will work for users.
The document provides 10 pieces of advice for software architects. It begins by introducing Eberhard Wolff and his background. Some of the key advice includes: understanding that the role of architect has changed with agile development and they are not managers; focusing on non-functional requirements and quality; caring about architecture and code quality rather than just diagrams; measuring code quality using tools; and ensuring proper dependency management to maintain architecture. The architect role is compared to that of a craftsman focusing on continual improvement rather than being separated from developers.
Using rapid prototying_for_design_iterationdrewz lin
This document discusses using rapid prototyping and iterative design to incorporate user feedback into the product development process. It advocates for:
1) Conducting user research like contextual inquiries and creating work models to understand user needs before design.
2) Developing low-fidelity paper prototypes to validate the product structure and features with users.
3) Iteratively testing prototypes with users, interpreting the feedback, and quickly modifying the prototypes.
4) Integrating this user-centered design process into an Agile development methodology with short sprints to incorporate user input at each stage of design.
This document discusses how Agile principles and practices can support ITIL frameworks. It advocates that development adopt Agile methods fully through automation, customer involvement, and focus on quality. It also stresses the importance of operations participating in development and allowing frequent changes. Adopting these approaches can improve service quality, reduce risks, and foster collaboration between teams. The document provides advice such as implementing process changes incrementally and ensuring both process owners and managers are involved.
Pre-Conference Course: UX and Agile: Making a Great Experience - UXPA International
In this tutorial for experienced practitioners you will learn how to manage work and make great experiences one sprint at a time. We'll look at common Agile methodologies such as Scrum and Kanban and what opportunities and risks are inherent for UX teams. We will look at team makeup, balancing longer-term research with production needs and strategies for making the most of design spikes. We'll also go through the pros and cons of a Sprint Zero and alternatives. Participants will come away with the tools they need to be successful in their Agile environment
This document discusses integrating user experience (UX) design into agile development processes. It describes common UX activities like user research, prototyping, and testing. It then provides examples of how companies have structured UX work within sprints, including frontloading UX work, biweekly design reviews, and participatory sketching sessions. The goal is to embed UX designers in teams to inform decisions early while still allowing flexibility.
This document discusses user story mapping. It begins by explaining what user stories are not, such as tasks, big stories, use cases, and documents. It then explains what user stories are, focusing on them being independent, negotiable, valuable, estimable, small, and testable pieces of functionality described using a Who/What/Why format. The document demonstrates how to slice user stories by things like screen, button, field, workflow step, acceptance criteria, role, and value. It notes some tips for slicing stories, like keeping them as stories and slicing more when estimating. Finally, it provides an overview of how to create a user story map by gathering user tasks, grouping them into activities, adding more detailed stories,
The document summarizes key points from a book about improving the customer experience. It discusses how companies can better understand customer needs by asking customers questions, observing how they use products, and listening to their feedback. The document also provides a case study of how a company called Skinit used these techniques like iterative design reviews to improve their product and significantly increase conversion rates. It emphasizes the importance of involving customers early in the design process and being willing to change designs based on what customers say, not just assumptions or guesses by the company.
The Agile Drupalist - Methodologies & Techniques for Running Effective Drupal...Adrian Jones
More and more clients are asking for Agile development for their projects, in particular the Scrum methodology, but do they really know what they are getting into? Both Waterfall and Scrum are viable methodologies, but each is best suited to particular situations, clients, and projects - neither can be considered the better methodology in all circumstances.
This presentation discusses the potential advantages of using Agile development for building sites in Drupal, but also the potential road-bumps and pitfalls.
The document discusses agile analysis and the role of the agile analyst. It describes common misconceptions about agile analysis and introduces techniques for effective agile analysis, including defining objectives, understanding the business domain through personas and goals, identifying requirements through user stories, scenarios, and story trees, and clarifying requirements through prototyping. The role of the agile analyst is described as a customer advocate, agile coach, facilitator, tester, and story librarian.
Exploring ux practices 4 product development agile2012drewz lin
This document describes a workshop on exploring Lean UX techniques and when they should be applied. [1] The goals of the workshop are to learn about Lean UX techniques that can be used at different development stages and do a collaborative design session to develop a minimum viable product (MVP) mobile app. [2] The workshop involves reviewing development stages and commonly used Lean UX techniques, brainstorming additional techniques, and doing a collaborative design exercise where teams research, scope, prototype, test and pitch a mobile networking app for conference attendees. [3] A retrospective is held at the end to discuss lessons learned.
The document discusses achieving better requirements on Agile projects. It begins by introducing traditional structured requirements approaches and how Agile differs. The main points covered include:
- User stories are the basis for requirements on Agile projects, bridging business goals to implementation. Stories should fit in iterations.
- Common pitfalls when dealing with Agile requirements include lack of context, unclear acceptance criteria, and not accounting for all work.
- The document recommends adopting seven habits to improve requirements, such as establishing scope and context, prioritizing based on business value, and elaborating requirements progressively with just enough detail. Acceptance tests should define requirements.
Presentation from Agile Base Camp 2 conference (Kiev, may 2010) about major activities to do before starting iterative development with one of the Agile methodologies.
Agile estimation and planning focuses on iterative development with short planning cycles. Teams work together in short iterations to deliver working software. Planning occurs through story mapping and estimation rather than detailed Gantt charts. Constant inspection and adaptation allows teams to respond to changes rather than rigidly following a predefined plan. Traditional waterfall planning fails because it relies on overly optimistic estimates far into the future and does not adapt to new information learned.
Designing an MVP that works for users (2 and 1/2 hours) @Lean UX NYC 2013Ariadna Font Llitjos
2 and 1/2 hour workshop that covers contextual inquiry, empathy map, user experience map, MVP, elevator pitch, flow diagrams, stories, paper prototype and guerrilla usability testing.
This document discusses user story mapping, an agile technique for planning and prioritizing product development work. It provides definitions of key terms like user activities, user tasks, and user stories. It also outlines the basic steps to do user story mapping, such as gathering user tasks, grouping and ordering them, adding more detailed stories, and prioritizing and breaking work into releases. The document notes that while agile aims to be simple, it is not always easy to implement due to competing interests. It suggests user story mapping can help with decision making, delivering value, and addressing scepticism.
This document discusses applying lean and agile principles to SharePoint development. It introduces lean concepts like Kanban and agile frameworks like Scrum and XP. It emphasizes techniques like automated testing, test-driven development (TDD), and continuous integration. The document acknowledges challenges in applying these techniques to SharePoint but provides examples of how to address them through practices like unit testing with isolation frameworks and continuous integration with PowerShell scripts.
Introduction to the Kanban as applied to software development. Delivered in Kirkland, WA in Nov 2011 by Dynacron Group.
Dynacron Group is an Agile software technology consulting firm. We provide training, consulting, and hands-on implementation for software projects in the Pacific Northwest.
User centric design focuses on optimizing the user interface around how users work rather than forcing users to change how they work. The presentation discusses adopting a user centric approach through:
1) Understanding user behavior and tasks rather than what developers wish users would do.
2) Integrating usability into all stages of design, development, and testing so all teams understand users.
3) Validating new development matches design through usability testing to prevent major defects in the final release.
This document provides 10 tips for software architects. It begins by introducing the author and their background. It then discusses that the role of a software architect is not well-defined and involves managing non-functional requirements and quality. Architects are responsible for defining and enforcing architecture. The document discusses how architects fit into agile development methodologies like Scrum. It argues that "architect" may not be the best metaphor and discusses an alternative view of architects as master craftsmen. The tips emphasize having your own opinion, improving vocabulary, eating your own dog food, avoiding broken windows, using domain-driven design strategically, caring about code and architecture, measuring and reducing complexity, and managing dependencies.
This document discusses various types of architecture including enterprise, solution, integration, software, business, and domain architecture. It also outlines key architecture principles and deliverables. The principles include target architecture, roadmap, view models, patterns used in the solution, peer review, and governance. Key deliverables include documentation of these principles, various views of the system, and references. Maintaining architecture is important to enable the solution, ease implementation through patterns and alignment, and support the system post-deployment through quality attributes.
ALE 2012 session description: In this highly collaborative workshop, we will apply a couple of UX practices and techniques, such as empathy maps, stakeholder maps, storyboards, sketchboards and paper prototype usability testing that will allow teams to focus on quick validation and delivery of killer apps that will work for users.
The document provides 10 pieces of advice for software architects. It begins by introducing Eberhard Wolff and his background. Some of the key advice includes: understanding that the role of architect has changed with agile development and they are not managers; focusing on non-functional requirements and quality; caring about architecture and code quality rather than just diagrams; measuring code quality using tools; and ensuring proper dependency management to maintain architecture. The architect role is compared to that of a craftsman focusing on continual improvement rather than being separated from developers.
Using rapid prototying_for_design_iterationdrewz lin
This document discusses using rapid prototyping and iterative design to incorporate user feedback into the product development process. It advocates for:
1) Conducting user research like contextual inquiries and creating work models to understand user needs before design.
2) Developing low-fidelity paper prototypes to validate the product structure and features with users.
3) Iteratively testing prototypes with users, interpreting the feedback, and quickly modifying the prototypes.
4) Integrating this user-centered design process into an Agile development methodology with short sprints to incorporate user input at each stage of design.
This document discusses how Agile principles and practices can support ITIL frameworks. It advocates that development adopt Agile methods fully through automation, customer involvement, and focus on quality. It also stresses the importance of operations participating in development and allowing frequent changes. Adopting these approaches can improve service quality, reduce risks, and foster collaboration between teams. The document provides advice such as implementing process changes incrementally and ensuring both process owners and managers are involved.
Pre-Conference Course: UX and Agile: Making a Great Experience - UXPA International
In this tutorial for experienced practitioners you will learn how to manage work and make great experiences one sprint at a time. We'll look at common Agile methodologies such as Scrum and Kanban and what opportunities and risks are inherent for UX teams. We will look at team makeup, balancing longer-term research with production needs and strategies for making the most of design spikes. We'll also go through the pros and cons of a Sprint Zero and alternatives. Participants will come away with the tools they need to be successful in their Agile environment
This document discusses integrating user experience (UX) design into agile development processes. It describes common UX activities like user research, prototyping, and testing. It then provides examples of how companies have structured UX work within sprints, including frontloading UX work, biweekly design reviews, and participatory sketching sessions. The goal is to embed UX designers in teams to inform decisions early while still allowing flexibility.
This document discusses user story mapping. It begins by explaining what user stories are not, such as tasks, big stories, use cases, and documents. It then explains what user stories are, focusing on them being independent, negotiable, valuable, estimable, small, and testable pieces of functionality described using a Who/What/Why format. The document demonstrates how to slice user stories by things like screen, button, field, workflow step, acceptance criteria, role, and value. It notes some tips for slicing stories, like keeping them as stories and slicing more when estimating. Finally, it provides an overview of how to create a user story map by gathering user tasks, grouping them into activities, adding more detailed stories,
The document summarizes key points from a book about improving the customer experience. It discusses how companies can better understand customer needs by asking customers questions, observing how they use products, and listening to their feedback. The document also provides a case study of how a company called Skinit used these techniques like iterative design reviews to improve their product and significantly increase conversion rates. It emphasizes the importance of involving customers early in the design process and being willing to change designs based on what customers say, not just assumptions or guesses by the company.
Sean and Mike will present on the history and lessons learned from developing the SDEC Mobile Conference application for Blackberry, Android, and Windows Phone 7. They will discuss developing for each platform and integrating the mobile apps with WCF services. Sean and Mike will demonstrate the Windows Phone 7 app and discuss what worked well, what they would change, and what they would not do again when developing for WP7.
This document provides an overview of a presentation titled "The ROR Trilogy Part I: A New Dev Hope" given by Amir Barylko. The presentation introduces Ruby and Ruby on Rails (ROR), covering topics such as dynamic languages, Ruby features, classes and objects, mixins, ROR conventions like MVC and scaffolding. It also lists resources for learning Ruby and ROR and concludes with a demo of a movie library application.
The document discusses how cloud service providers (CSPs) can help software developers by hosting their applications and services. It recommends partnering with a CSP to gain access to infrastructure, platforms, and services without having to build and maintain them. Developers should choose a CSP based on their technical capabilities, geographic coverage, security, scalability, and customer service/support. The case study profiles a payroll company that chose RackForce as their CSP due to its Canadian data centers, strong service level agreements, ease of use and support, security, and ability to scale on demand.
The document summarizes how the PSCAD Development Group transitioned to becoming an agile team. They identified problems with their previous approach and made changes such as improving communication within the rebuilt team, adopting iterative development cycles, introducing planning poker and automated testing, deploying software iteratively, and using paired programming and Kanban boards. The key steps taken included opening up to change, prioritizing adaptability, increasing collaboration, and continually experimenting with new agile methodologies.
The document discusses application portfolio management (APM) at the Manitoba government. It provides definitions and objectives of APM, including analyzing applications based on cost, value, quality and lifespan. It summarizes the APM work completed so far, including developing an inventory of 550 applications and analyzing trends in the portfolio. Analysis shows most applications are over 11 years old and the top 15 applications consume 50% of support resources. The overall aim is to optimize the application portfolio and guide investment decisions.
The document discusses security considerations for web applications that use Oracle products. It covers topics like using virtual private databases and Oracle Label Security to restrict user access to different parts of application and database data based on their roles. The document also explains how these Oracle security features can be implemented to allow different users like teenagers, parents, and administrators to only see data that they are authorized to access.
The document outlines an agenda for a session on monadic design patterns for the web. It discusses what to expect from the session, including fun, simplicity, engagement, and some challenge. It also discusses who the audience is and why monads are useful. The session will cover the monadic toolbox and provide simple and more complex examples of monadic patterns. It will discuss how monads can help manage complexity and provide abstraction.
This document provides an overview of applying Lean principles to transform services organizations. It discusses how Lean was applied to improve processes at Manitoba Immigration, focusing on registration, assessment, and employment solutions. The key aspects covered include reviewing Lean principles from both a production and customer viewpoint, taking a people-focused approach, and using tools like value stream mapping to eliminate waste and improve flow. Successful transformation requires executive commitment, employee engagement, and rigorous execution.
The document provides instructions for an Agile in a Day workshop. Participants are instructed to sit with others who have different levels of Agile experience. They then initial questions they want to learn and discuss challenges to adopting Agile. The workshop covers Agile concepts through activities like visioning, user stories, mapping stories and estimating. Participants work through an iteration, including planning, a standup and retrospective. They conclude by reviewing what they learned.
The document summarizes a presentation titled "Why User Experience matters for your App" given by David Alpert at a conference on October 17, 2011. The presentation discusses how customer expectations of software and digital experiences are rising due to influences from various parts of their lives and social media. It emphasizes that users are whole people, not just users, and stresses the importance of designing software with the user experience as the central focus from the outset.
The document introduces the Android operating system. It was created by Google and the Open Handset Alliance to provide an open-source alternative to Apple's iOS and compete in the growing smartphone market. Android uses the Linux kernel and a customized virtual machine called Dalvik to deliver the benefits of Java programming on mobile devices without the performance disadvantages of traditional Java VMs. The architecture is based around activities representing screens, views for building user interfaces, and intents for messaging and navigation between components.
1. The document provides an overview of Windows Azure offerings including Compute, Storage, SQL Azure, Virtual Network, AppFabric, and Marketplace.
2. It discusses the "7 Deadly Sins of Cloud Development" including under utilization of cloud resources, platform monogamy, poorly defined release cadence, always connected assumptions, synchronous application design, lack of load/failover testing, and lack of cloud reading.
3. The document includes demos of various Windows Azure features to illustrate how to avoid the sins.
Migrating an ASP.NET MVC application called Nerd Dinner to Windows Azure involves converting it to a web role, preparing the SQL database for SQL Azure, and configuring authentication. The presentation covers converting the project to a web role, deploying the SQL database to SQL Azure, and options for authentication including SQL Membership, Windows Azure Storage, and Claims-Based Authentication using Access Control Service.
This document discusses a software company's journey to adopting test-driven development (TDD) practices. It describes how the company initially launched its online scheduling system without TDD, which led to problems. A phone call made the company realize it needed to change its development approach to focus on quality. The company then transitioned to using TDD and other quality practices like continuous integration, code reviews, and acceptance testing. The document argues that TDD is not about the tests themselves but about quality, and lists benefits like growing the company and enjoying careers. It encourages readers to educate themselves on TDD, appoint a champion, and support their teams in getting started with these practices.
This document provides an overview of a presentation on advanced design patterns by Amir Barylko. It introduces Amir and lists his contact information and resources. It then outlines the topics that will be covered, including definitions of patterns and anti-patterns, examples of commonly used patterns like Chain of Responsibility and Proxy, and a discussion of which patterns the audience uses.
लालू यादव की जीवनी LALU PRASAD YADAV BIOGRAPHYVoterMood
Discover the life and times of Lalu Prasad Yadav with a comprehensive biography in Hindi. Learn about his early days, rise in politics, controversies, and contribution.
ग्रेटर मुंबई के नगर आयुक्त को एक खुले पत्र में याचिका दायर कर 540 से अधिक मुंबईकरों ने सभी अवैध और अस्थिर होर्डिंग्स, साइनबोर्ड और इलेक्ट्रिक साइनेज को तत्काल हटाने और 13 मई, 2024 की शाम को घाटकोपर में अवैध होर्डिंग के गिरने की विनाशकारी घटना के बाद अपराधियों के खिलाफ सख्त कार्रवाई की मांग की है, जिसमें 17 लोगों की जान चली गई और कई निर्दोष लोग गंभीर रूप से घायल हो गए।
13062024_First India Newspaper Jaipur.pdfFIRST INDIA
Find Latest India News and Breaking News these days from India on Politics, Business, Entertainment, Technology, Sports, Lifestyle and Coronavirus News in India and the world over that you can't miss. For real time update Visit our social media handle. Read First India NewsPaper in your morning replace. Visit First India.
CLICK:- https://firstindia.co.in/
#First_India_NewsPaper
17062024_First India Newspaper Jaipur.pdfFIRST INDIA
Find Latest India News and Breaking News these days from India on Politics, Business, Entertainment, Technology, Sports, Lifestyle and Coronavirus News in India and the world over that you can't miss. For real time update Visit our social media handle. Read First India NewsPaper in your morning replace. Visit First India.
CLICK:- https://firstindia.co.in/
#First_India_NewsPaper
18062024_First India Newspaper Jaipur.pdfFIRST INDIA
Find Latest India News and Breaking News these days from India on Politics, Business, Entertainment, Technology, Sports, Lifestyle and Coronavirus News in India and the world over that you can't miss. For real time update Visit our social media handle. Read First India NewsPaper in your morning replace. Visit First India.
CLICK:- https://firstindia.co.in/
#First_India_NewsPaper
Christian persecution in Islamic countries has intensified, with alarming incidents of violence, discrimination, and intolerance. This article highlights recent attacks in Nigeria, Pakistan, Egypt, Iran, and Iraq, exposing the multifaceted challenges faced by Christian communities. Despite the severity of these atrocities, the Western world's response remains muted due to political, economic, and social considerations. The urgent need for international intervention is underscored, emphasizing that without substantial support, the future of Christianity in these regions is at grave risk.
https://ecspe.org/the-rise-of-christian-persecution-in-islamic-countries/
15062024_First India Newspaper Jaipur.pdfFIRST INDIA
Find Latest India News and Breaking News these days from India on Politics, Business, Entertainment, Technology, Sports, Lifestyle and Coronavirus News in India and the world over that you can't miss. For real time update Visit our social media handle. Read First India NewsPaper in your morning replace. Visit First India.
CLICK:- https://firstindia.co.in/
#First_India_NewsPaper
16062024_First India Newspaper Jaipur.pdfFIRST INDIA
Find Latest India News and Breaking News these days from India on Politics, Business, Entertainment, Technology, Sports, Lifestyle and Coronavirus News in India and the world over that you can't miss. For real time update Visit our social media handle. Read First India NewsPaper in your morning replace. Visit First India.
CLICK:- https://firstindia.co.in/
#First_India_NewsPaper
projet de traité négocié à Istanbul (anglais).pdfEdouardHusson
Ceci est le projet de traité qui avait été négocié entre Russes et Ukrainiens à Istanbul en mars 2022, avant que les Etats-Unis et la Grande-Bretagne ne détournent Kiev de signer.
Federal Authorities Urge Vigilance Amid Bird Flu Outbreak | The Lifesciences ...The Lifesciences Magazine
Federal authorities have advised the public to remain vigilant but calm in response to the ongoing bird flu outbreak of highly pathogenic avian influenza, commonly known as bird flu.
Recent years have seen a disturbing rise in violence, discrimination, and intolerance against Christian communities in various Islamic countries. This multifaceted challenge, deeply rooted in historical, social, and political animosities, demands urgent attention. Despite the escalating persecution, substantial support from the Western world remains lacking.
Shark Tank Jargon | Operational ProfitabilityTheUnitedIndian
Don't let fancy business words confuse you! This blog is your cheat sheet to understanding the Shark Tank Jargon. We'll translate all the confusing terms like "valuation" (how much the company is worth) and "royalty" (a fee for using someone's idea). You'll be swimming with the Sharks like a pro in no time!
Why We Chose ScyllaDB over DynamoDB for "User Watch Status"ScyllaDB
Yichen Wei and Adam Drennan share the architecture and technical requirements behind "user watch status" for a major global media streaming service, what that meant for their database, the pros and cons of the many options they considered for replacing DynamoDB, why they ultimately chose ScyllaDB, and their lessons learned so far.
12062024_First India Newspaper Jaipur.pdfFIRST INDIA
Find Latest India News and Breaking News these days from India on Politics, Business, Entertainment, Technology, Sports, Lifestyle and Coronavirus News in India and the world over that you can't miss. For real time update Visit our social media handle. Read First India NewsPaper in your morning replace. Visit First India.
CLICK:- https://firstindia.co.in/
#First_India_NewsPaper
1. When User Stories aren’t
enough
Active Architecture
@tbunio
Bornagainagilist.wordpress.com
2. Agile Review
Agenda User Stories
What‟s missing?
Active Architecture
Examples
• Me
• Agile Review
- Agile Question
• User Stories and User Story Process
• What‟s missing?
• Active Architecture
• Examples
• Questions
3. Agile Review
Me User Stories
What‟s missing?
Active Architecture
Examples
• Investors Group for 12 years
- Software Developer
- DBA/Data Architect
• Protegra for 10 years
- DBA/Data Architect
- Project Manager
- Agile Team Member
• Project Manager/Application Architect/Tester
• @tbunio
• Bornagainagilist.wordpress.com
4. Agile Review
Agile Interests User Stories
What‟s missing?
Active Architecture
Examples
• Agile on fixed price contacts
• Agile in large enterprises
- Government
- Private
• Agile estimating
• Agile tools
• Agile database development
5. Agile Review
Learning outcomes User Stories
What‟s missing?
Active Architecture
Examples
• Describe what Active Architecture is
• Describe the benefits of Active Architecture and what
some limitations of User Stories might be
• Contrast Active Architecture to other forms of
Architecture documentation
6. Agile Review
Agile Question User Stories
What‟s missing?
Active Architecture
Examples
• What do people think is the main shortcoming of Agile?
8. Agile Review
Traditional User Stories
What‟s missing?
Active Architecture
Examples
• Textual Status Reports
• Detailed project plan at the start of the project
• Discrete project roles
• Serial project phases
• Large and voluminous requirements documentation
• Large testing phase
- Usually can result in manual testing
• „Big Bang‟ deployment
- Usually can result in manual deployments
9. Agile Review
Agile User Stories
What‟s missing?
Active Architecture
Examples
• Visual Project Management
• Not a detailed project plan at the start of the project
• Cross-functional team members
• Iterations
• Lean requirement documentation
• Testing phase integrated in all activities
- Automated testing
• Multiple deployments
- Automated deployments and continuous integration
11. Agile Review
Agile Thoughts User Stories
What‟s missing?
Active Architecture
Examples
• Being quicker and doing less for the sake of being
quicker and doing less is not being Agile
- It needs to result in more value to the client and project
• We need to be careful to not throw the Baby (good
traditional processes) out with the Bathwater (bad
traditional processes)
• In particular
- All Up front Design and Architecture
- All Estimating
• Traditional and Agile are not mutually exclusive
processes
- There are opportunities for hybrid approaches
12. Agile Review
These are not the processes User Stories
What‟s missing?
you are looking for… Active Architecture
Examples
13. Agile Review
User Stories User Stories
What‟s missing?
Active Architecture
Examples
Copyright : The Sherpa Project – www.thesherpaproject.com
14. Agile Review
User Stories User Stories
What‟s missing?
Active Architecture
Examples
Copyright : The Sherpa Project – www.thesherpaproject.com
15. Agile Review
User Stories User Stories
What‟s missing?
Active Architecture
Examples
Copyright : The Sherpa Project – www.thesherpaproject.com
16. Agile Review
What User Stories are… User Stories
What‟s missing?
Active Architecture
Examples
A small piece of • As a user, I want to
functionality that login with my
provides some value password, so that I
to a user can gain access to
the site.
“A place holder for a conversation.”
17. Agile Review
What User Stories are… User Stories
What‟s missing?
Active Architecture
Examples
I Independent *
N Negotiable (can be prioritized)
V Valuable (to a user)
E Estimable
S Small
T Testable
18. Agile Review
Formats User Stories
What‟s missing?
Active Architecture
Examples
By the book:
As a [role], As a [user]
I want to I want to
[some action], [login with my pwd]
so that so that
[goal] [I can gain access to
the site]
19. Agile Review
Formats User Stories
What‟s missing?
Active Architecture
Examples
As a
Who [user]
I want to
What [login with my pwd]
so that
Why [I can gain access to
the site]
The “by the book” format is great for learning, but
at its core, it is just Who/What/Why
20. Agile Review
User Story Process User Stories
What‟s missing?
Active Architecture
Examples
• Typically User Story will be compiled using a variety of
methods.
• These include User Story Mapping and other traditional
methods
- Interviewing
- Workshops
- Focus groups
21. Agile Review
User Story Estimation User Stories
What‟s missing?
Active Architecture
Examples
• All the User Stories are then typically estimated relatively
• Planning Poker is then done either on:
- An iteration by iteration basis
- A few iterations in advance
• Planning Poker will typically confirm the Requirements
and enhance aspects of the design
• In addition, Planning Poker usually also touches on
aspects of detailed design and architecture.
22. Agile Review
What is missing? User Stories
What‟s missing?
Active Architecture
Examples
• Since we are doing design iteratively…
- How do we minimize rework?
• Could designs in later iterations cause rework?
- How do we know our designs are consistent across iterations?
• What if different team members are responsible for different aspects?
• What if team composition changes?
- How do we know they are no gaps in our design?
• Are there user stories that we are missing?
• And since User Stories are from a user event
perspective, are we missing „System‟ stories that define
background details?
23. Agile Review
What are we missing? User Stories
What‟s missing?
Active Architecture
Examples
• User Stories and Planning Poker sessions will answer
these questions eventually
• But is there a light-weight process that can answer these
questions earlier to minimize rework?
25. Agile Review
Shared Design Vision User Stories
What‟s missing?
Active Architecture
Examples
• After we have compiled and estimated the User Stories,
do we have a shared vision of the design and ultimate
solution?
- At a high level?
26. Agile Review
Without a Shared Vision User Stories
What‟s missing?
Active Architecture
Examples
27. Agile Review
User Experience Visioning User Stories
What‟s missing?
Active Architecture
Examples
• In David Alpert‟s talk yesterday on User Experience
Design, he mentioned the process of „thinking through‟
the User Experience
- After this development went very smoothly
• This provided the awareness of context of the bigger
picture for all that were involved.
• I am essentially proposing a Lean/Agile „thinking through‟
process for design or architecture
28. Agile Review
What would the Document User Stories
What‟s missing?
look like? Active Architecture
Examples
29. Agile Review
Traditional Design User Stories
What‟s missing?
Documents Active Architecture
Examples
• Large
• Textual
• Passive State
30. Agile Review
Agile Design Document User Stories
What‟s missing?
Active Architecture
Examples
• Light-weight
• Graphical and textual
• Active State
31. Agile Review
Agile Design Document User Stories
What‟s missing?
Active Architecture
Examples
• Active versus Passive
• Traditional design document is passive like a road map
• Active Architecture is active like trip directions
• They don‟t describe the road, they describe how the road
is to be travelled or used.
32. Agile Review
Three types of Agile User Stories
What‟s missing?
Requirements Active Architecture
Examples
• User Stories – Stories of how the User interacts with
the application or manual processes
• Component Conversations – Conversations between
components of the application
• Technical Tasks – Technical tasks that the applications
needs to perform within a component
34. Agile Review
Agile Requirements User Stories
What‟s missing?
Active Architecture
Examples
• It is thought that User Stories and Tests can be all the
documentation you require on an Agile project
• But we know we can‟t create tests for everything
• How can we create complete user stories for:
- Portfolio Rebalancing Engine
- Payroll Engine
- Scheduling or Matching Engines
36. Agile Review
Component Conversations User Stories
What‟s missing?
Active Architecture
Examples
• Ensures User Stories are consistent in how functionality
is handled across components
• Ensures User Stories do not create an undue amount of
rework when an original story is encountered in a later
iteration
• Ensures that the entire solution has been thought
through at a high level
• Reduces the chance that a story will be discovered late
that will require earlier stories to be revisited
• Ensures technical tasks are implemented consistently
across components
37. Agile Review
Component Conversation User Stories
What‟s missing?
Active Architecture
Examples
• Ensures the creation of complex back-end high level
requirements that would be inefficient and possibly
inconsistent to define on a story by story basis
• Ensures the creation of complex back-end high level
requirements that may not be covered easily by user
stories
• Components conversations can be reviewed to ensure
we have all the system functionality covered and there
are no gaps.
40. Agile Review
Solution Driven Development User Stories
What‟s missing?
Active Architecture
Examples
• “I believe in what I like to term Solution Driven
Development. If you can‟t or haven‟t envisioned the
solution, how can you start executing the project? Some
people would say that not having to envision the total
solution is Agile. I believe it is unprofessional. Some
would say that the solution will change anyway so why
spend the effort envisioning and planning when it is likely
to change? I believe that we can’t proceed unless we
have a shared vision on what we are creating.”
41. Agile Review
Welcome Changing User Stories
What‟s missing?
Requirements Active Architecture
Examples
• “welcome changes to the requirements in response to
evolving business needs”.
• Two assumptions:
- “Changes are welcome to the requirements” – This means we
know what the baseline of the requirements are. Otherwise, how
could we know what a change is?
- “Respond to evolving business needs” - We are responding to
evolving business needs. This assumes that we have a baseline
of current business needs.
42. Agile Review
Active Architecture User Stories
What‟s missing?
Objectives Active Architecture
Examples
• To think things through from a requirements and design
perspective
• To envision and design the solution to ensure that the
solution is complete, consistent, and cohesive
43. Agile Review
Potential Format User Stories
What‟s missing?
Active Architecture
Examples
• [#][Component A] does
[primary action].[object].[additional action] by
[Action].[Component B] when [event]
44. Agile Review
Facebook example – User Stories
What‟s missing?
Browsing Friends Active Architecture
Examples
- [1][SuggestedFriends] does [create].[SuggestedFriendList] by [filtering
common connections across all friends].[Connection-DB] when [user
logs on]
- [2][FacebookUser] does
[Sends].[FriendInvitation] by
[selectingconnectioninvitebutton].[SuggestedFriendList] when
[User clicks on send friend request]
- [3][FacebookUser] does
[Updates].[SuggestedFriendList] by
[selectingconnectionhidebutton].[SuggestedFriendList][HideFriendList]
when
[User clicks on hide friend]
- [4][FacebookUser] does
[Accept].[FriendInvitation] by
[selecting accept invitation].[PendingInvitations] when
[User clicks on accept invitation]
45. Agile Review
FaceBook example – User Stories
What‟s missing?
Learnings Active Architecture
Examples
• There is a process that creates these
SuggestedFriendLists separate from the User
interactions
• There is a Connection-DB that is used to create this
SuggestedFriendList and possibly the HideFriendList
• There is an object that contains the Pending Invitations.
(And possibly a similar concept for other pending
objects)
• There is the concept of a persisted HideFriendList to
ensure suggestions that have been selected to be
hidden will not appear again.
51. Agile Review
Email Example User Stories
What‟s missing?
Active Architecture
Examples
• Although the User Story map will help to flesh out the
functionality in Iterations, what about the following items?
- Message delivery and transmission (and confirmation)
- How and when will messages be stored?
• How can they be recovered?
- Junk mail and approved sender functionality
- Encryption/Decryption functionality
• For novel solutions, it usually isn‟t enough to just
document the user interactions requirements
52. Agile Review
Active Architecture User Stories
What‟s missing?
Guidelines Active Architecture
Examples
• Maximum of 2-3 days for a 3-6 month project
• Accompanied by a solution design diagram on a white
board
- Take pictures after review with team to gain consensus
- You can‟t make me use Visio… not gonna do it..
• These two deliverables can be all that is required for
Agile design documentation
55. Courage
• Most of what I‟ve presented are other thoughts and
guidelines with my thoughts and guidelines
• I encourage you to try them out and tailor them to your
own situation
• How else can we make Agile processes even better?