Winning Hearts and Minds: How to Embed UX from Scratch in a Large Organization
Michele Ide-Smith presents the lessons learned in the process of introducing UX principles and techniques into a large organization through a series of small steps.
Content in this box provided by our Sponsor:
![]() |
VersionOne is recognized by agile practitioners as the leader in agile project management tools. By simplifying the planning and tracking of agile projects, we help teams deliver better software faster. Today more than 30,000 teams from over 170 countries use VersionOne. Agile Made Easier @ VersionOne.com.
![]() |
![]() |
FREE Agile Project Management Software
See for yourself why VersionOne is the most popular agile project management tool on the planet.
Agile Whitepapers
Agile Resources
![]() |
The Agile Toolkit
Getting Started with Agile
Agile Customer and Management Practices
VersionOne Case Studies
Michele Ide-Smith presents the lessons learned in the process of introducing UX principles and techniques into a large organization through a series of small steps.
QCon is now less than 2 weeks away and there are only 100 spots left before QCon London completely sells out. Register before March 2nd and receive £75 off. QCon is organized as a practitioner-driven conference designed for people influencing innovation in their teams: team leads, architects, project managers, engineering directors
VersionOne have recently released the results of their State of Agile Development Survey for 2011, and as always it gives an interesting insight into Agile adoption and trends.

Rajneesh Namta shares the lessons he’s learned while automating software tests on a recent Agile project. The techniques he recommends illustrate how the Agile principles we follow when building software apply equally as well to building an automated regression test suite: start small, build iteratively and incrementally, prioritize, focus on value, work transparently, respond quickly to change.

"The CERT Oracle Secure Coding Standard for Java" book covers the rules for secure coding using Java programming language and its libraries with the goal to help Java developers eliminate insecure coding practices that can lead to vulnerable code. InfoQ spoke with book authors about how the security rules discussed in the book compare to other security coding frameworks.
Barry Hawkins considers as necessary to have a development process but in the same time maintaining a critical view of it in an attempt to improve it and make it fit within the current context.
Joel Semeniuk discusses ways of making better project estimates excluding guessing as much as possible.

Recorded at the 10th anniversary of the agile manifesto signing, Jim Highsmith discusses how he works with executive management teams to introduce and integrate agile techniques into enterprise organizations from both the business and IT sides. He defines adaptive leadership and discuses adaptive ALM, continuous delivery, lean and Kanban methods.

Aino Corry discusses various aspects of Agile Retrospectives: how to get them accepted, core principles, length, frequency, structure, techniques for handling problems, and much more.

This mini-book offers an easy to follow 10 step guide to taking the initial plunge and start using Lean principles to optimizing value and flow in your system. Each step consists of a section explaining “why” followed by examples of specific tools, practices and rules that have helped other teams better understand and optimize their system.

Scrum, arguably the fastest-growing Agile methodology, is well described in the original Scrum books, which tend to be read once and put aside. Scrum is a framework with simple rules. This Scrum Checklist will help you to remember these simple rules in the heat of daily work and stress. It enable you to create an enjoyable and productive work environment with your Scrum-Team.

Scrum and Kanban are two flavours of Agile software development. So how do they relate to each other? Part I illustrates the similarities and differences between Kanban and Scrum, comparing for understanding, not for judgement.Part II is a case study illustrating how a Scrum-based development organization implemented Kanban in their operations and support teams.
For those getting started with Agile, this book offers a detailed first-person account of how one Swedish company implemented Scrum and XP with a distributed team of 40 people, and how they continuously improved their process over a year’s time.

This book guides the reader on crafting their own agile adoption strategy focused on their business values and environment. This strategy is then directly tied to patterns of agile practice adoption that describe how many teams have successfully (and unsuccessfully) adopted them. Business values are also a component of these patterns so your adoption is always focused on addressing your particular environment.

Domain Driven Design is a vision and approach for designing a domain model that reflects a deep understanding of the business domain. This book is a short, quickly-readable summary and introduction to the fundamentals of DDD; it does not introduce any new concepts; it attempts to concisely summarize the essence of what DDD is, drawing mostly Eric Evans' book, as well other sources since published such as Jimmy Nilsson's Applying Domain Driven Design, and various DDD discussion forums.