Dear Experts

My organization is currently adopting the Agile methodology for Project Management of projects (However, they only seem to adopt the part that mean less documentation/work)

As someone who works on behalf of the business, it is up to me to ensure that the requirements have been met.  However, many of the user stories are 9by design) fairly vague.  But in order to test something, details are required.  From what I can tell, these details are kept in the developer's head.  But is there any opart of the Agile methodology that I can state they need to follow in order to document the detials of such user stories (because at the moment I just waste time searching for the right person to ask)

An example may be: As a user I need to ensure that all the mandatory fields are completed before I move to the next step

Where are the mandatory fields defined?

Thanks in advance!

 Hi there,

A couple of related concepts which I have recently heard articulated, and which resonated with me are:

1. A promise to communicate: Even though the user stories may not have all of the detial that we have been accustomed to in a thick BRD, they do identify a requirement that will bring value, and it therefore on everyone in the agile team to promise to communicate about it at the appropriate time so that all the details are shaken out.
2. "Social contract": the above promise relies on an understanding between everyone involved that the team are responsibile to each other and to the outcome, and that the detailed questions will be asked when necessary - rather than just the easiest assumptions made!

All the best with the agile adoption!

Cheers,

pete