Out Of The Mouths Of Clients

[DimPrawn]

What could go wrong?

In my experience this:

[barrydidit]

He hasn't been on that Yorkshire Agile course, yet

HTH.

BIDI.

There's time...

Agile Yorkshire | Leeds, York, Bradford, Sheffield

There's also Tuesday 12th January - David Turner, An Agile Journey (or How I Learned to Stop Worrying and Love Change!) + Ash Winter, Tested To Death - Agile Yorkshire | Leeds, York, Bradford, Sheffield should anyone be looking for stuff to do on their trip to Leeds....

[vetran]

Isn't that Aggro???

FTFY

[TheFaQQer]

I am not a BA or a Dev, but can anyone please tell me how is this even possible?!

I have gone back and asked how do they know what to build, but I am scared of the answer to be fair!

You know what to build based on the functional specification - that tells you what you need it to do. Then you build it, then you document it, to ensure that the documented design matches the actual build.

Otherwise, you have to keep getting the technical design document updated with every section of code which doesn't match the original document, or the document is vague and fluffy.

Take your pick.

[DimPrawn]

You know what to build based on the functional specification - that tells you what you need it to do. Then you build it, then you document it, to ensure that the documented design matches the actual build.

Otherwise, you have to keep getting the technical design document updated with every section of code which doesn't match the original document, or the document is vague and fluffy.

Take your pick.

It's better to replace the functional specification with ever increasing set of automated tests. That way as the specification and the software evolves you can clearly see if the software meets the specification.

Nothing worse than 1,000,000 page written spec. Write a 1,000,000 lines of test harnesses.

[SpontaneousOrder]

You only need design docs for particularly hard to understand things. It's normal to produce technical documentation either at the end (or probably easier immediately after you've finished that part of the development).

The only solutions that I've seen that really NEED technical docs (apart from a few flow-charts to help the support guys, etc) are the ones that have been done really tulipty.

otherwise, why would you need them (for 95% of projects)?

[MrMarkyMark]

You know what to build based on the functional specification - that tells you what you need it to do.

<Placeholder for Simon Mac saying they do not have a Functional Spec Either>

Now that's real Agile

[xoggoth]

Not public sector by any chance? I was once hired to address an issue that made the newspapers at the time, expensive defence helicopters brought from the US that had been sitting in a barn for a couple of years due to lack of documentation.

[SpontaneousOrder]

Not public sector by any chance? I was once hired to address an issue that made the newspapers at the time, expensive defence helicopters brought from the US that had been sitting in a barn for a couple of years due to lack of documentation.

Public sector is the only place I've ever produced a piece of design documentation!

[woohoo]

asked about what happens if an error is found and a new version of code is created?

Word or word answer is:

The technical design documents are all created at the end of development

I'm having trouble understanding the question (I'm very literal).