I have been asked to help with a workshop being run by a team of people doing some business change work. “Introduce them to the Atern way of working,” I was asked. Intriguing.
DSDM originated on software development projects but recent versions, especially Atern, have been written with non-IT projects in mind. I have, however, never used it outside of software development. So how, I am wondering, will Atern techniques, roles and practices translate? How do we define MUST Have requirements, for instance? How do we estimate the work involved? How do we plan?
I have a number of ideas, of course. I am presenting an overview of my suggested approach to the team on Monday, as well as facilitating a requirements-gathering session. It should be interesting.