You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 29, 2022. It is now read-only.
When you have to make major changes, it can be easy to feel like you failed. Where did it go wrong? Who planned this project, anyway? And sometimes there are process lessons to learn, but not always. We use an iterative (or "agile") process because we want to plan for changes along the way. Learning from experience, and knowing when to pivot, is part of the plan. Don't try to remove it from your process — try to bake it in!
This happens at all levels — from company structure and project management to UX and code implementation details. Sometimes you need a draft to test, before you can see the right path. OddBird has been through this many times, and we can still struggle with it...
The text was updated successfully, but these errors were encountered:
mirisuzanne
changed the title
Agile for a purpose: learning, pivoting, recovering, and moving on
Post: Learning, pivoting, recovering, and moving on
Sep 14, 2016
When you have to make major changes, it can be easy to feel like you failed. Where did it go wrong? Who planned this project, anyway? And sometimes there are process lessons to learn, but not always. We use an iterative (or "agile") process because we want to plan for changes along the way. Learning from experience, and knowing when to pivot, is part of the plan. Don't try to remove it from your process — try to bake it in!
This happens at all levels — from company structure and project management to UX and code implementation details. Sometimes you need a draft to test, before you can see the right path. OddBird has been through this many times, and we can still struggle with it...
The text was updated successfully, but these errors were encountered: