Published August 15, 2017
Choosing The Right Project Methodology
There’s more than one way to skin a cat, as they say. But who is “they” and why would anyone want to skin a cat?
We’ll use the phrase metaphorically here, as it’s generally intended, to mean that we all do things differently. The way that we go about managing projects depends on our team, stakeholders, goals, users, scopes, and budgets. As a result, we pick what works best in the situation: Agile, Waterfall, for example, or a Hybrid of the two.
Consider the following before you choose a project methodology:
- The team/talent: What expertise and interests does your team have, and how will their talents inform the way the project gets done?
- Who are the stakeholders and clients? How do they prefer to work, and what expectations do they have about their involvement in the process?
- What is the scope of the project? What do you need to get done?
- What will your deadlines look like? How much time you do you need to get the work done?
There is no right or wrong choice to make here. There is only the approach that allows your team to shine. Fewer teams choose Waterfall these days, as it relies on a rigid schedule of deliverables, approvals, and handoffs. Many are blending Agile methods, which focus on iteration and collaboration, with Waterfall techniques, especially when stakeholders expect a more formalized process of milestones, deliverables, and review.
Previous UX Thoughts of the Day:
Get the insight you need to write tidy text.
Learn these tips and write amazing user interfaces.
Find out why good UX is an accessible experience for everyone.
Learn how to distinguish voice from tone.
UX thoughts to inspire you to do something differently in your design work.
UX Thought of the Day
Delivered right to
UIE values your privacy.
We will never sell your e-mail address.