Agile & UX
Get flash to fully experience Pearltrees
The Cooper Journal: Lean UX, Product Stewardship, and Integrated Teams
Several emergent themes in software design and development are converging into a new way of working: Entrepreneurs understand the strategic value of user experience design in the guise of Steve Blank's customer development and Eric Ries' lean startup Each of these ideas have significant impact on the way user experience designers approach their work and how businesses structure their design and development efforts.
Startup Monthly (Palo Alto, CA) - Meetup
Startup Socials SF Party May 2012 You will meet new people and party with like minded entrepreneurs, investors, startups, professionals and party people in non-formal... Learn moreSteve Blank
One of the confusing things to entrepreneurs, investors and educators is the relationship between customer development and business model design and business planning and execution. I was in Washington D.C. last week presenting at the ARPA-E conference. I spent the next day working with the National Science Foundation on the Innovation Corps , and talking to congressional staffs about how entrepreneurial educational programs can reshape our economy. (And I even found time to go to the Spy Museum .) One of the issues that came up is whether the new lexicon of entrepreneurial ideas – Customer Development, Business Model Design , Lean , Lean LaunchPad class, etc. – replace all the tools and classes that are currently being taught in entrepreneurship curriculums and business schools.
Facebook, early 2006 Sometimes, you need to be horribly, embarrassingly wrong to remind yourself to keep an open mind. This is my story of my failure to understand Facebook’s potential. In 2006, I was working on a new ad network business that experimented a lot with targeting ads with social network data, broadly known as “retargeting” now.
Andrew Chen (@andrewchen)
Balanced Team is sponsoring an evening event March 11, 2011 in Austin TX during SxSW interactive. Please join us for spirited conversation, engaging lightning talks, tasty drinks and snacks on the roof deck and a round of fabulous door prizes. Thanks to our fantastic sponsors, Adaptive Path, UIE, {new context}, Rosenfeld Media and LUXr! To [...]
Balanced Team
With more development moving to an Agile process, User Experience and Design (UXD) professionals are faced with the task of adapting their activities, deliverables, and even their own role to an Agile development process. Education on general Agile development principles and activities is readily available (for example, see IBM Agile resources ). While Agile development principles and best practices such as continuous user feedback and iterative development are familiar to UXD professionals, the focus on efficiency and time-boxed iterations can present a challenge.
Design - An Agile approach to User Experience and Design
Maturing Usability: Quality in Software, Interaction, and Value contains a collection of writings from various experts in the field of usability and user interface development. It provides an understanding of how current research and practice has contributed towards improving quality issues in software, interaction and value. I wrote Chapter 4 which describes how usability fits into the Agile lifecycle . Other chapters look at how using development tools can enhance the usability of a system, and how methods and models can be integrated into the process to help develop effective user interfaces; theoretical frameworks on the nature of interactions; techniques and metrics for evaluation interaction quality; the transfer of concepts and methods from research to practice; assessments of the impact that a system has in the real world; and how to focus on increasing the value of usability practice for software development and on increasing value for users.
Maturing Usability: Quality in Software, Interaction, and Value
1. When Should You Do Initial Agile Requirements Modeling? Agile Model Driven Development (AMDD) , see Figure 1 , explicitly includes an initial requirements envisioning effort during Iteration 0 of an agile project (what some processes might call the Warm-UP, Inception phase, or Initiation phase). Initial requirements envisioning is particularly important for scaling agile software development techniques to larger, more complex, or globally distributed development (GDD) efforts.
Requirements Envisioning: An Agile Best Practice
1. When Should You Do Initial Agile Architecture Modeling? Agile Model Driven Development (AMDD) , see Figure 1 , explicitly includes an initial architectural modeling effort during Iteration 0 of an agile project (what some processes might call the Warm-UP, Inception, or Initiation phase). Initial architecture modeling is particularly important for scaling agile software development techniques to large, complex, or globally distributed development (GDD) efforts.
Architecture Envisioning: An Agile Best Practice
Agile Best Practice: Prioritized Requirements
Figure 1 overviews the Scrum approach to managing requirements where your software development team has a stack of prioritized and estimated requirements which need to be addressed ( Scrum calls this prioritized stack a "product backlog"). There are several important points to understand: New requirements are prioritized by your project stakeholders and added to the stack in the appropriate place.
Roles on Agile Teams: From Small to Large Teams
Two common questions of people new to agile will ask include "what are the roles on an agile team?" and "how do you organize an agile team?" The goal of this article is to address these questions by examining how you would do so for a relatively small agile team , perhaps of 15 or less people, and for a large agile team , perhaps of 50 people or more. For teams in between these sizes you will need to tailor a solution somewhere in between. The roles and organization structures described in this article are meant to be representative -- your approach may differ slightly because you are in a different situation.Best Practices for Agile/Lean Documentation
Ideally, an agile document is just barely good enough , or just barely sufficient, for the situation at hand. Documentation is an important part of agile software development projects, but unlike traditionalists who often see documentation as a risk reduction strategy, agilists typically see documentation as a strategy which increases overall project risk and therefore strive to be as efficient as possible when it comes to documentation. Agilists write documentation when that's the best way to achieve the relevant goals, but there often proves to be better ways to achieve those goals than writing static documentation.The Agile System Development Life Cycle (SDLC)
I'm often asked by clients to facilitate workshops overviewing the ideas presented in the Agile Manifesto and agile techniques such as Test-Driven Design (TDD) , database refactoring , and agile change management . One issue that many people seem to struggle with is how all of these ideas fit together, and invariably I found myself sketching one or more pictures which overview the life cycle for agile software development projects. I typically need one or more pictures because the scope of life cycles change -- some life cycles address just the construction life cycle, some address the full development life cycle, and some even address the full IT life cycle. Depending on your scope, and how disciplined your approach to agile software development is, you will get different life cycle diagrams.We’re sorry, but we were unable to find what you were looking for. We have opened the left menu to display all sections within the site or, perhaps searching will help.
HOT Topics! Article
I’m Jeff Patton and I consider myself a sleeves-rolled-up practitioner of Agile Software Development . I place particular emphasis on creating context specific approaches that lead to the holistic design, development, and delivery of successful products. I consult for a variety of organizations helping them adopt Agile software development, and adopt practices that improve the quality and frequency of delivery of the products they build. (I hope they end up having more fun as well.)