Process & Methodologies
An analyst is embedded in the delivery process: the team picks up the requirements, and the way the team works decides in what form and when those requirements are needed. In Waterfall everything is prepared up front and in full; in Agile it comes in small portions, sprint by sprint. Understanding that rhythm matters as much as knowing the notations themselves.
There are three skills here: choose a methodology and know its ceremonies, frame a goal so it is verifiable (SMART), and split a large item into deliverable pieces (decomposition). Common traps are confusing which approach is iterative, treating grooming as a one-time event, and decomposing into pieces that cannot ship on their own. The full map lives in the layers below.
Topic map
- Agile vs Waterfall — iterative delivery vs sequential phases and when each approach fits.
- Scrum ceremonies — sprint, planning, retro, and grooming: what happens in each.
- SMART goals — the five criteria that turn a fuzzy wish into a verifiable goal.
- Task decomposition — why a large backlog item is split into smaller independent pieces.
- Decomposition techniques — which axes a task is split by and how to pick the right one.
- Feasibility and value assessment — how an analyst prepares a high-level requirement for development.
Common traps
| Mistake | Consequence |
|---|---|
| Swapping which approach is iterative vs sequential | You describe Agile and Waterfall wrong — a basic failure |
| Claiming Agile forbids change | You miss the very essence of Agile — welcoming change |
| Treating grooming as a one-time event | The backlog is not ready for the sprint; planning stalls |
| Forgetting a SMART letter (often Relevant or Time-bound) | A goal with no deadline or no link to the objective — not trackable |
| Splitting a task into interdependent pieces | The pieces cannot be shipped and tested on their own |
| Coding a requirement "as-is" without assessment | Constraints and risks are missed; you automate a broken process |
Interview relevance
Process is asked to check whether you will fit a real team: whether you know the sprint rhythm, can set verifiable goals, and can split large items. A candidate who explains decomposition as "independent pieces, each carrying value" immediately gets ahead of one who "cuts the task into chunks."
Typical checks:
- The essence of Agile and how it differs from Waterfall; which context suits which.
- What a sprint, planning, retro, and grooming are and how they differ.
- The SMART acronym and why a goal needs each criterion.
- Which axes a task is decomposed by and how to pick the split.
Common wrong answer: "Agile is when there is no plan and no documentation." In fact Agile is iterative delivery of working increments with welcomed change and feedback; there is a plan and documentation, they are just not frozen up front but refined as you go.