In the Agile software development world, time is of the essence – or rather design time becomes a precious commodity. Taking the time to conduct in-depth user research, then create and explore innovative design solutions becomes an expensive luxury that isn’t always affordable. But what happens if there is a way to not just streamline the UX research and design process, but to actually produce better results for it?
As UX Designers in Agile dev teams we commonly grapple with challenges such as:
- Being allowed the time to go through the creative exploration process, when a Dev team is waiting for to you to finish so that they can start.
- Finding a balance between being Lean in practices, while exploring alternative innovative ideas and solutions.
- Explaining to Devs that lo-fi prototypes are more a communication tool and than a finalised deliverable
What’s the solution?
At ThoughtWorks we spend a lot of time trying to evaluate our approach and improve our techniques. I’ll share some of the Lean UX methods and approaches that we’ve been embracing to get out of the deliverable business and to start becoming an integrated part of Agile software delivery teams to collaboratively develop great experiences in short time frames. I’ll cover topics and techniques including:
- Engaging stakeholders and the Dev team early using collaborative design
- Rapid production
- Conducting lightweight research
- Rapid iterations
- Managing expectations
- Asking for more time
- Communicating progress through regular showcases
DocOps: Documentation at the Speed of AgileMary Connor
Presented at Keep Austin Agile 2016: How to we make documentation "Agile", given the Agile Manifesto? How do you get into the Definition of Done? What does "DocOps" mean, in the simplest and broadest terms? What should your requirements be for a DocOps transformation, and how do you find a tool stack that fits them? Where do you start, and how do you escape a waterfall reengineering of your legacy docs?
The really really basic start to Social Media. ALERT: Facebook & Twitter are NOT the only social media platforms, because they are the most popular in Arkansas, we will start there!
RfS 160 MW GRID CONNECTED SOLAR PV in UTTAR PRADESHHarish Sharma
As part of JNNSM Phase-II Batch-III, Tranche-VII, SECI has invited setting up of grid connected Solar PV Projects in Uttar Pradesh, on “Build Own Operate” basis for an aggregate capacity of 160 MW. Projects selected based on this RfS shall be given “Viability Gap Funding” in line with terms and conditions of this RfS. SECI shall enter into Power Purchase Agreement (PPA) with the Bidders selected based on this RfS for purchase of solar power selected for a period of 25 years based on the terms, conditions and provisions of the RfS.
RfP FOR 1000 MW SOLAR PV POWER PROJECTS UNDER JNNSM PHASE II BATCH-III TRANCH...Harish Sharma
Bids are invited for the Selection of “1000 MW Grid Connected Solar PV Projects in Karnataka under JNNSM Phase-II Batch-III, Tranche-V” for Setting up of Solar PV Projects in India on “Build Own Operate” basis and selling the Solar Power to Solar Energy Corporation of India Ltd.(SECI)
Last date for the bid submission is 29/03/2016 up to 14:00 Hrs (IST)
Awareness of design smells - indicators of common design problems - helps developers or software engineers understand mistakes made while designing and apply design principles for creating high-quality designs. This presentation provides insights gained from performing refactoring in real-world projects to improve refactoring and reduce the time and costs of managing software projects.
Tugbot - Testing Framework for Docker ContainersNeil Gehani
Social Testing for Docker ecosystem. Tugbot provides simplified and standardized testing for apps in container clusters. It enables teams to share test containers.
DocOps: Documentation at the Speed of AgileMary Connor
Presented at Keep Austin Agile 2016: How to we make documentation "Agile", given the Agile Manifesto? How do you get into the Definition of Done? What does "DocOps" mean, in the simplest and broadest terms? What should your requirements be for a DocOps transformation, and how do you find a tool stack that fits them? Where do you start, and how do you escape a waterfall reengineering of your legacy docs?
The really really basic start to Social Media. ALERT: Facebook & Twitter are NOT the only social media platforms, because they are the most popular in Arkansas, we will start there!
RfS 160 MW GRID CONNECTED SOLAR PV in UTTAR PRADESHHarish Sharma
As part of JNNSM Phase-II Batch-III, Tranche-VII, SECI has invited setting up of grid connected Solar PV Projects in Uttar Pradesh, on “Build Own Operate” basis for an aggregate capacity of 160 MW. Projects selected based on this RfS shall be given “Viability Gap Funding” in line with terms and conditions of this RfS. SECI shall enter into Power Purchase Agreement (PPA) with the Bidders selected based on this RfS for purchase of solar power selected for a period of 25 years based on the terms, conditions and provisions of the RfS.
RfP FOR 1000 MW SOLAR PV POWER PROJECTS UNDER JNNSM PHASE II BATCH-III TRANCH...Harish Sharma
Bids are invited for the Selection of “1000 MW Grid Connected Solar PV Projects in Karnataka under JNNSM Phase-II Batch-III, Tranche-V” for Setting up of Solar PV Projects in India on “Build Own Operate” basis and selling the Solar Power to Solar Energy Corporation of India Ltd.(SECI)
Last date for the bid submission is 29/03/2016 up to 14:00 Hrs (IST)
Awareness of design smells - indicators of common design problems - helps developers or software engineers understand mistakes made while designing and apply design principles for creating high-quality designs. This presentation provides insights gained from performing refactoring in real-world projects to improve refactoring and reduce the time and costs of managing software projects.
Tugbot - Testing Framework for Docker ContainersNeil Gehani
Social Testing for Docker ecosystem. Tugbot provides simplified and standardized testing for apps in container clusters. It enables teams to share test containers.
Software Architecture: Principles, Patterns and PracticesGanesh Samarthyam
Are you a developer or designer aspiring to become an architect? Do you want to learn about the architecture of open source applications? Do you want to learn software architecture through case studies and examples? If you have answered “yes” to any of these questions, this presentation is certainly for you. This presentation will introduce you to key topics in software architecture including architectural principles, constraints, non-functional requirements (NFRs), architectural styles and design patterns, viewpoints and perspectives, and architecture tools. A special feature of this workshop: it covers examples and case studies from open source applications. What’s more, you’ll also get exposed to some free or open source tools used by practicing software architects.
Contents overview:
* Introduction to SA
* Overview of design principles, patterns and architectural styles
* Realising quality requirements (NFRs)
* Case studies: Architecture of well-known open source applications
* Tools: Free or open source tools for software architects
* Must to read books on software architecture
(Presented in OSI Days workshop in Bangalore on 19th Nov 2015).
Discussion about message queue systems, like Beanstalkd pros and advantages.
Asynchronous: Queue it now, run it later.
Decoupling: Separates application logic.
Resilience: Won't take down your whole application if part of it fails.
Redundancy: Can retry jobs if they fail.
Guarantees: Makes sure that jobs will be processed.
Scalable: Many workers can process individual jobs in a queue.
Elasticity & "Spikability": When your application hits the front page of Hacker News, you see unusual traffic
Buffering: operate at peak efficiency by offering a buffer layer
Profiling: Can aid in identifying performance issues.
The new way to extend VSTS Build and ReleaseJesse Houwing
Extending the new Build and Release features of Visual Studio Team Services (and TFS) helps you turn your scripts into easily re-usable build steps. There are a number of options, from simple scripts to complete custom tasks built using C#, PowerShell or Typescript. We’ll walk through the options and will pros and cons each and quickly walk through the process of building and releasing a custom task to the Visual Studio Marketplace.
26 septembre 2016
Groupe Excel + Power BI
Cette présentation couvre tous les aspects de Power BI, en passant par l'importation et/ou la connection à diverses sources de données, la création de modèles de données, la création de rapports, la création de rôles de sécurité, la publication sur le service web, l'installation de passerelles, la programmation de rafraîchissement de données et la consommation de rapports.
Today, constant innovation defines our marketplace. Businesses must respond to customer expectations for better digital experiences. How do leading organisations launch successful new products and respond rapidly to external change? How do they move beyond the simple need to innovate to actively practising innovation every day?
Innovation is such a big word that people over complicate it. They put too much emphasis on producing something innovative and become attached to their ideas and outputs. Instead the opposite is required. To be innovative you need to responsive and adaptable. You need to be willing to try an idea, assess, adjust and continue moving forward.
These concepts of learning by doing, failing fast, adapting to change are all core principles behind Agile practices. They are the reason why iterative development exists – and the reason it can be so effective. Agile software development has moved from niche to mainstream, but still provides challenges for design and innovation.
We will show you how proven Agile principles and techniques can enable product innovation. Using lean thinking, fast-feedback cycles, and by taking lots of small bets we will show how to consistently speed new ideas into the market.
Join us for some stories from the trenches of Agile product delivery. Hear about the failures and successes of brave organisations that have dared to do things differently. You’ll see practical principles and techniques you could be using today.
Ben Melbourne & Diana Adorno
Pecha Kucha - Edward Tufte Information Design books reviewBen Melbourne
This is a book review, in the Pecha Kucha format, of some Edward Tufte's book. It includes some of my favourites of the beautiful historical examples he uses to explain how his points of information design.
Creating a single, consistent experience across the Queensland Government website
Presented by David Beal & Andrew Ramsden, Queensland Government
The Queensland Government is a diverse and complicated organisation, spanning over 13 different departments, covering everything in the state from running the treasury to issuing fishing licenses. As more and more services have been provided online the Government's web presence has also grown to reflect this diversity and complexity, which can make it hard for the public to realise the full benefits of the available services. Through their hard work researching, designing and implementing a common, single website experience, the Queensland Government Online team is in the process of changing this to make Queensland a world leader in the online space. In this case study, David and Andrew will share the highs, lows and challenges they have faced along their journey.
General UX activities & process overviewBen Melbourne
Here's a somewhat somewhat lengthy (by still far from comprehensive) presentation introducing and detailing the process and activities involved in Agile UX. The content focuses on introducing the basic steps of UX and explaining what they are.
It's liberally referenced from anywhere I could cut and paste from, and includes lots of links for more reading, where more comprehensive explanations of each activity can be found.
Join us for a conversation about interface and interaction design trends for the coming year (and beyond). Our first ixda event of 2011 will survey a selection of emerging technologies and evolving patterns in designing products and services. We'll discuss as a group and single out a few common-interest topics to get in-depth with over the next series of events.
A list of topics will be presented at the meeting, but suggestions are welcome and encouraged. Bring your knowledge and enthusiasm and let's get started on making 2011 a cool and interesting year for Brisbane IXDA.
Software Architecture: Principles, Patterns and PracticesGanesh Samarthyam
Are you a developer or designer aspiring to become an architect? Do you want to learn about the architecture of open source applications? Do you want to learn software architecture through case studies and examples? If you have answered “yes” to any of these questions, this presentation is certainly for you. This presentation will introduce you to key topics in software architecture including architectural principles, constraints, non-functional requirements (NFRs), architectural styles and design patterns, viewpoints and perspectives, and architecture tools. A special feature of this workshop: it covers examples and case studies from open source applications. What’s more, you’ll also get exposed to some free or open source tools used by practicing software architects.
Contents overview:
* Introduction to SA
* Overview of design principles, patterns and architectural styles
* Realising quality requirements (NFRs)
* Case studies: Architecture of well-known open source applications
* Tools: Free or open source tools for software architects
* Must to read books on software architecture
(Presented in OSI Days workshop in Bangalore on 19th Nov 2015).
Discussion about message queue systems, like Beanstalkd pros and advantages.
Asynchronous: Queue it now, run it later.
Decoupling: Separates application logic.
Resilience: Won't take down your whole application if part of it fails.
Redundancy: Can retry jobs if they fail.
Guarantees: Makes sure that jobs will be processed.
Scalable: Many workers can process individual jobs in a queue.
Elasticity & "Spikability": When your application hits the front page of Hacker News, you see unusual traffic
Buffering: operate at peak efficiency by offering a buffer layer
Profiling: Can aid in identifying performance issues.
The new way to extend VSTS Build and ReleaseJesse Houwing
Extending the new Build and Release features of Visual Studio Team Services (and TFS) helps you turn your scripts into easily re-usable build steps. There are a number of options, from simple scripts to complete custom tasks built using C#, PowerShell or Typescript. We’ll walk through the options and will pros and cons each and quickly walk through the process of building and releasing a custom task to the Visual Studio Marketplace.
26 septembre 2016
Groupe Excel + Power BI
Cette présentation couvre tous les aspects de Power BI, en passant par l'importation et/ou la connection à diverses sources de données, la création de modèles de données, la création de rapports, la création de rôles de sécurité, la publication sur le service web, l'installation de passerelles, la programmation de rafraîchissement de données et la consommation de rapports.
Today, constant innovation defines our marketplace. Businesses must respond to customer expectations for better digital experiences. How do leading organisations launch successful new products and respond rapidly to external change? How do they move beyond the simple need to innovate to actively practising innovation every day?
Innovation is such a big word that people over complicate it. They put too much emphasis on producing something innovative and become attached to their ideas and outputs. Instead the opposite is required. To be innovative you need to responsive and adaptable. You need to be willing to try an idea, assess, adjust and continue moving forward.
These concepts of learning by doing, failing fast, adapting to change are all core principles behind Agile practices. They are the reason why iterative development exists – and the reason it can be so effective. Agile software development has moved from niche to mainstream, but still provides challenges for design and innovation.
We will show you how proven Agile principles and techniques can enable product innovation. Using lean thinking, fast-feedback cycles, and by taking lots of small bets we will show how to consistently speed new ideas into the market.
Join us for some stories from the trenches of Agile product delivery. Hear about the failures and successes of brave organisations that have dared to do things differently. You’ll see practical principles and techniques you could be using today.
Ben Melbourne & Diana Adorno
Pecha Kucha - Edward Tufte Information Design books reviewBen Melbourne
This is a book review, in the Pecha Kucha format, of some Edward Tufte's book. It includes some of my favourites of the beautiful historical examples he uses to explain how his points of information design.
Creating a single, consistent experience across the Queensland Government website
Presented by David Beal & Andrew Ramsden, Queensland Government
The Queensland Government is a diverse and complicated organisation, spanning over 13 different departments, covering everything in the state from running the treasury to issuing fishing licenses. As more and more services have been provided online the Government's web presence has also grown to reflect this diversity and complexity, which can make it hard for the public to realise the full benefits of the available services. Through their hard work researching, designing and implementing a common, single website experience, the Queensland Government Online team is in the process of changing this to make Queensland a world leader in the online space. In this case study, David and Andrew will share the highs, lows and challenges they have faced along their journey.
General UX activities & process overviewBen Melbourne
Here's a somewhat somewhat lengthy (by still far from comprehensive) presentation introducing and detailing the process and activities involved in Agile UX. The content focuses on introducing the basic steps of UX and explaining what they are.
It's liberally referenced from anywhere I could cut and paste from, and includes lots of links for more reading, where more comprehensive explanations of each activity can be found.
Join us for a conversation about interface and interaction design trends for the coming year (and beyond). Our first ixda event of 2011 will survey a selection of emerging technologies and evolving patterns in designing products and services. We'll discuss as a group and single out a few common-interest topics to get in-depth with over the next series of events.
A list of topics will be presented at the meeting, but suggestions are welcome and encouraged. Bring your knowledge and enthusiasm and let's get started on making 2011 a cool and interesting year for Brisbane IXDA.
Technoblade The Legacy of a Minecraft Legend.Techno Merch
Technoblade, born Alex on June 1, 1999, was a legendary Minecraft YouTuber known for his sharp wit and exceptional PvP skills. Starting his channel in 2013, he gained nearly 11 million subscribers. His private battle with metastatic sarcoma ended in June 2022, but his enduring legacy continues to inspire millions.
PDF SubmissionDigital Marketing Institute in NoidaPoojaSaini954651
https://www.safalta.com/online-digital-marketing/advance-digital-marketing-training-in-noidaTop Digital Marketing Institute in Noida: Boost Your Career Fast
[3:29 am, 30/05/2024] +91 83818 43552: Safalta Digital Marketing Institute in Noida also provides advanced classes for individuals seeking to develop their expertise and skills in this field. These classes, led by industry experts with vast experience, focus on specific aspects of digital marketing such as advanced SEO strategies, sophisticated content creation techniques, and data-driven analytics.
Connect Conference 2022: Passive House - Economic and Environmental Solution...TE Studio
Passive House: The Economic and Environmental Solution for Sustainable Real Estate. Lecture by Tim Eian of TE Studio Passive House Design in November 2022 in Minneapolis.
- The Built Environment
- Let's imagine the perfect building
- The Passive House standard
- Why Passive House targets
- Clean Energy Plans?!
- How does Passive House compare and fit in?
- The business case for Passive House real estate
- Tools to quantify the value of Passive House
- What can I do?
- Resources
Maximize Your Content with Beautiful Assets : Content & Asset for Landing Page pmgdscunsri
Figma is a cloud-based design tool widely used by designers for prototyping, UI/UX design, and real-time collaboration. With features such as precision pen tools, grid system, and reusable components, Figma makes it easy for teams to work together on design projects. Its flexibility and accessibility make Figma a top choice in the digital age.
7. The Agile Manifesto
Individuals and interactions ...over processes and tools
Working software ...over comprehensive documentation
Customer collaboration ...over contract negotiation
Responding to change ...over following a plan
http://agilemanifesto.org/
This is my personal story about my journey in to the Agile world. Full discloser: I am a ThoughtWorker . ThoughtWorks is an Agile Software Development consultancy. We are sponsors . It ’s not the official ThoughtWorks party line. It ’s my story about what I ’ ve learnt . Which is heavily influenced by my time working at TWs.
The promised land Before ThoughtWorks, I had little experience with Agile .When I first started working in an Agile environment I was excited to have finally reached the promised land.
Waterfall I was well aware of the problems with Waterfall… • Painful stakeholder reviews . • Having to endlessly review, revise and annotate wireframes . • Devs not building things as specified . … and I thought all these problems would magically disappear with Agile.
Happy Days All of a sudden:Devs would become my best friends My wireframes wouldn ’t be near as detailed . Document version numbers would stop getting in to double figures.My designs might get launched in the same year. I realised that these things didn ’ t just happen automatically . Agile opens up an exciting new way of working , but it also presents a new set of challenges . To experience the benefits I had to adjust the way I worked .
These are the some of the things I ’ve learnt about Agile UX. • 3 x Challenges • 3 x Adjustments • Tools & Techniques I ’ve learnt to use
Let me start by giving a quick intro to what I ’ve learnt to be some of the key parts of agile. This stuff is important because we need to learn to be part of the process of building software .
The Agile Manifesto Put together by a group of Devs in 2001 , looking to better ways of working. Before working in an Agile environment I didn't really know much more about Agile than this. It made a lot of sense to me on face value. I ’ve learnt to appreciate: A statement of values, not rules . Agile pureists: Both sides are important , but those on the left are valued more.
In practice the Agile is all about:Highly collaborative Multifunctional teams Do enough to learn Learn as you goBe adaptable The only measure of value in Working Software . It ’ s not: A prescribed set of methods It is: A mindset and approach When consulting clients think they can just learn a process... There are common tools, but each team adapts to a way that works for them.
Story Cards The key tool of Agile teams. Business value (aka Requirements) captured as user stories. As a…I want to…So that…The user…The functionality…The Business value.As a Conference attendee, I want to learn about Agile UX, so that I improve my own UX practice. Different levels - Epics & Stories
Iterations/Sprints The Agile development cycle.Short, time boxed periods , usually 2-4 weeks.Used for adaptive planning, measurement and feedback .
Showcases At the end of each iteration . For stakeholder feedback. Adapt and adjust based on what is learnt.
Short, sharp cycles Build, test, learn, adjust. As short as possible. Validated learning.I ’ve been used to feedback loops that take months-years. Agile shortens these to weeks.
Challenge #1: Not having time to explore ideas and find innovative solutions In an Agile environment I found that design time became a precious commodity . My traditional user-centered design methods started to encounter problems. I didn ’ t get the time to conduct in-depth user research, analyze the findings, write them up, then design an extensive solution.It was hard to find the time when a Dev team is waiting for to me to finish so that they can start. As a UXer I felt like you have a steamroller bearing down on me while I screamed: ‘ Stop, I need to explore more ideas! ’
Challenge #2: Feeling like time spent exploring ideas is a waste when you ’ re trying to be Lean. The traditional creative process involves playing with designs and seeing where they lead . Exploration and refinement . The designs themselves may get discarded , but the learnings from them fold back in to the overall solution. Once I started to embrace a Lean way of thinking, I felt like I was deliberately wasting time . This test and learn approach is actually a core part of Agile, but I had to just to adjust to do it a different way.
Challenge #3: Getting out of the deliverable business. My traditional approach of producing shiny, all-encompassing deliverables didn ’t work in an Agile process. I didn ’ t have the time and they were usually out-of-date by the time I finished them. On the flip side, it didn ’t work when I just started producing lots of low-fidelity prototypes and then handed them over to the Devs. Is still encountered communication breakdowns .
These are some of the ways I ’ve learnt to adjust my practice to overcome these challenges and get the most out of Agile.
Adjustment #1: UX as a facilitator, not just a designer. Change my role in the team.I let go of control of every little detail and empowered the team .Use my research skills to take the team on a journey of understanding and empathizing with the user . Became an Information Radiator . Not the sole source of knowledge. Gave everyone the knowledge. There was still be plenty of design work required for me as a designer, but I was able to start sharing the load.
Adjustment #2: Design as a continuous activity. Make design an ongoing activity , not just a phase. Agile UX isn ’t just about breaking our activities into small chunks , i.e. mini-waterfall. It’s about changing our approach and how we work.
The Continuous movement Other fields are embracing the “ Continuous ” approach . Product management is embracing the Lean Startup movement. Launching a MVP, testing and proving a proposition, then continuing to evolve it. The Dev community is doing Continuous Delivery to make this possible. The ability to release software regularly (i.e. daily rather than a few big releases a year) is allowing teams to reduce feedback cycles . Testing and learning rapidly. As designers we need to embrace this mindset .
Adjustment #3: Do just-enough, just-in-time. Just-in-time design does what it says in the tin .Don ’t try to do everything upfront, start by sketching a vision , then figure out the details as you go. Make decisions at the last responsible moment . Change is relentless . If you do too much upfront, the requirements will probably change by the time you get your designs out there.
These are some of the tools and techniques I ’ve been using to make these adjustments.
Live Below the Line Example & Shameless plug About - Charity campaign to raise awareness of world poverty, and raise money to help those living in extreme poverty. The Challenge - $2 a day, 5 days. Timeframe Initial launch in 1.5 months. Full public campaign launch in 3 months - yesterday. The Project challenge New site from scratch, replace off-the-shelf product. Lots of features Limited time 4 countries 3 organisations - Oaktree, Global Poverty Project, MakeBelieve 2 key stakeholders, Dan & Guy (UK) Great cause we wanted to do everything for. The Team 6-8 Back-end Devs 1 Front-end Dev 1 BA 1 UX Releases Start Nov. Jan 19 - UK Partners (7 weeks) Feb 15 - Oz O-Week Mar 1 - NZ Country May - Campaign week
Live Below the Line Example & Shameless plug About - Charity campaign to raise awareness of world poverty, and raise money to help those living in extreme poverty. The Challenge - $2 a day, 5 days. Timeframe Initial launch in 1.5 months. Full public campaign launch in 3 months - yesterday. The Project challenge New site from scratch, replace off-the-shelf product. Lots of features Limited time 4 countries 3 organisations - Oaktree, Global Poverty Project, MakeBelieve 2 key stakeholders, Dan & Guy (UK) Great cause we wanted to do everything for. The Team 6-8 Back-end Devs 1 Front-end Dev 1 BA 1 UX Releases Start Nov. Jan 19 - UK Partners (7 weeks) Feb 15 - Oz O-Week Mar 1 - NZ Country May - Campaign week
Live Below the Line Example & Shameless plug About - Charity campaign to raise awareness of world poverty, and raise money to help those living in extreme poverty. The Challenge - $2 a day, 5 days. Timeframe Initial launch in 1.5 months. Full public campaign launch in 3 months - yesterday. The Project challenge New site from scratch, replace off-the-shelf product. Lots of features Limited time 4 countries 3 organisations - Oaktree, Global Poverty Project, MakeBelieve 2 key stakeholders, Dan & Guy (UK) Great cause we wanted to do everything for. The Team 6-8 Back-end Devs 1 Front-end Dev 1 BA 1 UX Releases Start Nov. Jan 19 - UK Partners (7 weeks) Feb 15 - Oz O-Week Mar 1 - NZ Country May - Campaign week
Collaborative design workshops Start projects use collaborative design workshops. Whole Project Team : Stakeholders, Devs.Everyone in a room sketching Ideas about what the product should/could be.This creates a Sketchboard . This involves the UX as a facilitator .
Sketchboards The output of Collaborative Design Workshops On a wall - anyone can see and contribute to it. Shared vision , everyone is bought in to as they contributed to it.
This is an example of where we sketched out what a mobile app would look like in 30 mins . It allowed the team to visualise what it would look like and how much work would be involved. This helped us quickly make a strategic decision not to go ahead with it without wasting any time on it.
Write Stories & Epics Use this shared vision to:• Write Epics + Stories.• Develop prototypes to test and validate.
Use Iteration 0 to get setup Iteration 0 is the initial project ramp-up time that happens after kickoff. Development Environments, Project plans, etc. This time gives us some time to get ahead. Setting up frameworks, IA, Global Nav, Tasks & Flows, Templates etc
Rapid Iterations Short time boxed periods, focus on small parts of functionality . The iteration cycle allows us to shorten feedback loops . Quickly turn design ideas into working code – when can then be tested and improved .We no longer have to wait months/years to see if our design works, we can do it immediately.
Co-Location Co-locate yourself with and become part of the Project Team. ...this was our gun team. There shouldn ’t be a wall. Multidisciplinary teams all working in one place sharing ideas is a key principle of Agile.Don ’t send emails, have a quick conversation . Open the kimono . Lots of Devs have never worked with a UXer before. They want to learn to work with us as well.
Design Walls As the details start to emerge turn your Sketchboard in to a Design Wall . Claim space alongside the Project team ’s card wall. Put our sketches/wireframes/visual designs on the wall .Painting a picture/vision then filling in details as you go . This will ‘radiate’ details of the UX and become a source of truth.
Lightweight production Don ’t aim to capture every detail. Capture just enough , then have a conversation.Sometimes a paper sketch is enough, others a hi-fi mock is required. The conversation is important.
Conducting lightweight research Bring user feedback in to the team. Go guerrilla . Run three sessions every Friday. Or every iteration. Make it easy for the team to watch.Post-it notes, not PowerPoint.Put the findings in to action straight away.
Add usability fixes to the backlog Become part of the process. Identify usability fixes Write up stories for them Add them to the backlog and prioritise . Product owner can make an informed decision about what to do next, something new or a fix. Avoid the tension of us trying to squeeze small fixes in in an unstructured way.
Looking back on my experience... Now that I ’ve learnt to adjust and over come those initial challenges , Agile has helped me to become a better designer . It has forced me to focus on providing value , not just pretty documents . Teaching me to work in quick, lightweight ways . It has allowed me become part of the Dev to the team , allowing greater team collaboration that leads for far better outcomes than I could have produced by myself. It has empowered me by speeding up my feedback loops .Now I can try something and learn about how well it works quickly . All these things have allowed me to use my time to do what I do best – create great experiences .