EppsNet Archive: Feedback

Visibility and Feedback

 

Forgive my ignorance. How do increased visibility and tighter feedback loops manage and reduce risk? Get in your car. Drive to a winding road. Get up to a decent speed. Close your eyes for two minutes. Then come back and ask your question again. — Ron Jeffries, Yahoo Groups (kanbandev) Read more →

Customer Engagement

 

You want to actively elicit feedback from end users using short development cycles or by using prototypes and models during analysis. A good feedback cycle has the appearance of causing problems. It will cause emergent and latent requirements to surface. That means rework: the value of prototypes is that they push this rework back into analysis, where it has more value. And most important, good end user engagement changes end user expectations. It is only by participating in a feedback loop that’s grounded in reality that customers get the opportunity they need to reflect on what they’re asking for. If your customer changes their expectations in the process, you’ve both learned something. Embracing change doesn’t just mean reacting to it: it means providing the catalysts that accelerate it. — James O. Coplien and Gertrud Bjørnvig, Lean Architecture for Agile Software Development Read more →

Don’t Look Back

 

In uncertain conditions the main question should not be: “Why didn’t your performance yesterday conform to the original plan?” Rather, it should be: “What kind of feedback can help you learn faster and perform better tomorrow?” — “Ninety-Nine Rules for Managing ‘Faster, Better, Cheaper’ Projects” Read more →