"No detailed design documentation"?
This plank of Agile Development, appled to Design, is often misunderstood as
"No detailed design effort"
But start with bad basic ideas, and you can prototype, test & fix all you like, but you won't get a good design out of it. You'll be out in that desert, walking in circles.
You still need to design the UX of key activities, just wide enough and deep enough that you're sure they'll hang together well, before you start coding the "features" the UX requires.
I can plug my design skills into any design effort, in any type of development process...>>
1) I design with our range of users, their wants and abilities in mind:
2) Of the dozens of "rules of thumb" my designs will in particular:
3) Plus, experience has made these less common skills second nature: