home page

my blog posts

Agile Does Not Mean “No Requirements”

My second post for my employer Tribridge on a series about Agile misconceptions:

In the first post in my series about Agile Software Development, I discussed the most common misconception that our clients have about Agile. Specifically, we often hear the assumption that there is no planning or analysis when preparing for an Agile project, and that the development team starts building the application immediately. In today’s post, I would like to address another common misconception about writing requirements and the process that our team uses to gather and record requirements in order to deliver high quality Agile projects.

Read the full article on tribridge.com 


Comments are closed.