Win a copy of Succeeding with AI this week in the Artificial Intelligence and Machine Learning forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • Liutauras Vilda
  • Junilu Lacar
  • Tim Cooke
  • Jeanne Boyarsky
  • Knute Snortum
Saloon Keepers:
  • Stephan van Hulst
  • Tim Moores
  • Tim Holloway
  • Carey Brown
  • Piet Souris
  • salvin francis
  • fred rosenberger
  • Frits Walraven

Writing a POC as part of agile project

Ranch Hand
Posts: 70
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Can we write up a proof of concept as part of an agile project? If so then how do we divide up the cycle times or should this be done as part of initial requirements phase?
Posts: 14112
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I don't see why you couldn't implement a POC. Can you please elaborate your question on dividing up cycle times? Which cycle times are you talking about, and why do they need to be divided up?
Posts: 31
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
When I think of a POC (proof of concept), I think of prototypes, or lets do some coding to see if it works. Why would you write it up first, rather than just doing it? Can you explain a little better? POCs are a big part of agile. Before spending a lot of time planning something that might not work, create a story for a "spike" or POC.

I have the same questions about cycle times that Ilja had.

I am displeased. You are no longer allowed to read this tiny ad:
Two software engineers solve most of the world's problems in one K&R sized book
    Bookmark Topic Watch Topic
  • New Topic