
Agile project methodology is a decision-making model. In agreeing to take on a project and use agile methodology to govern the project makeup, one is agreeing to work closely with project stakeholders. When I say work closely, I mean much closer than the standard meetings and engagements encouraged by other methodologies. Decisions will be made all along the timeline. There has to be a framework setup that ensures discussions towards these decisions can be made continuously.

What about when you are unsure about what needs to be done on a project?
What about when you are unsure about what needs to be done on a project? This is where agile methodology seems to have a few more answers than a step-by-step planning method.
Focus on the outcomes of the project.
This approach focuses on the outcomes of the project. Perhaps you need something done by a certain date. This means your timeline is fixed. You can do 100 different things towards the outcome you want. You try something towards the outcomes needed. If it fails, change it or try something new towards the outcome you want. To make this decision you use more relevant information that you now are aware of.
Resolve to make a considered selection of next steps.
Based on the information you have available to you, select the best option. By best option, I mean the set of actions that have the best chance of moving you closest to your goal. Resolve to make a considered selection of next steps.
Agile project methodology is a decision-making model.
Key is that you make a decision. This decision can change things being done based on the information you now have at your disposal. Furthermore, you have better information NOW than at the start. Using that information you change, pivot, respond to the new set of information. This steers you closer to your target. By making the adjustments needed you can achieve your end goal.
Need an example of a simple project plan?
Check this article out on Personal Plans.