agile processes - Integration card at the end of a user story (TDD) -

agile processes - Integration card at the end of a user story (TDD) -

our team develops tdd , when implementing new features @ end of story when cards turn greenish comes "the integration card", means putting implemented components play nice each other. sense bad card, because means, noone tried code in real life in tests , integration card means trying out , create working.

is agile practice set integration card @ end of every story results in new feature? or should part of every task card when possible integrate existing code?

here 2 cents:

tdd on has nil way of working described in question. agile / scrum / lean / kanban in opinion.

writing unit tests before write code practice, guys doing if understand correctly.

i agree that's bit of weird postpone actual integration of code end of sprint. if hell breaks loose, got nil @ end of sprint. in other words, potential shippable product not exist until lastly risky card done.

if want break through way of working, i'd consider googling continuous integration. there strive integrate code possible, in order find integration bugs possible.

so long story short:

no it's not agile practice, and yes improve integrate every done, done, done task

hope helps create step towards true agile/lean team! trust instincts, do :).

tdd agile-processes