Agile Principles #4: Product Owner and Engineer relationships
Time for Agile principle number four, where we talk about the relationship between product owner and engineer:
Business people and developers must work
together daily throughout the project.
In the post on agile principle number two, I gave the example of a Secret Santa management system, as an example of how being able to accommodate changing requirements can benefit a project. As a refresher, here’s the key story points of the project:
- A user should be able to sign up
- A user should be able to log in
- A user should be able to get a recipient assigned
- A user should be able to add notes to their recipient
Agile-style planning, or “A man, a plan, a canal. Every week.”
In my last post, I gave a brief intro to Agile, and I promised a post about simple planning. Here you go.
So, to plan software, it should be simple. You know what you want, so just figure out a plan for making it happen, and then follow the plan. What could be easier? If you’re planning the entire project up front, nothing could be harder.
If you’re reading this post, you already know that plans change. That’s why we do Agile. We plan often, and we review the plan daily.







