As I become more engulfed in the ways of Agile I will continue to share my experiences, frustrations, questions, and ah ha moments. I welcome any and all feedback from the CSMs of the world, as well as thoughts from other newbies.

One big change change driven by starting to build earlier is that of condensing up-front design work down to Just Enough. In other words, we go from doing a lot of analyzing and creating a lot of documents, sometimes for months, to committing to start delivering some kernel of the real product within weeks of project inception.

Our development process spans 6 different Trello boards. The focal point of all of these boards is the Current Development board. The goal of all the other boards is to feed cards (representing either an enhancement or a bug, more on these in a minute) into the Current Development board and specifically into its Next Up column. The Next Up column is THE single prioritized list that all of the product team (developers & designers) looks at when they’re ready to take a new card to work on.

really don't agree with this, UX as product owner in #agile team should equally own and be responsible for product

The role of the user experience designer is changing. It’s becoming less about ‘owning’ experience and actual design and more about facilitation and collaboration, says Lee Allen of TH_NK

RT @whatterz: Essential UX Layers for Agile and Lean Design Teams #ux #agile #lean

RT @Folletto: I got a bit more in-depth with my Dot Loop process, with more examples and explanations: #agile #simple

Most of the software world has realised that Big Design Up Front (BDUF) doesn’t work well in software. But lots of developers struggle with this notion when it applies to architecture and design, surely you can’t start coding, right? You need some level of understanding before you can start work.

RT @andybudd: Agile+UX