Complexity Sizing a ticket

Complexity

| Value | Guidelines |5| * Extremely complex task ||* Multiple dependencies on other stories or systems ||* Requires a skill set that is missing in the team but important ||* Story is difficult to accurately describe ||* Many unknowns ||* May require high level of refactoring ||* Extensive research required ||* Requires difficult judgment calls ||* Story implementation might have significant impact outside its scope 4 ● A very complex task ● May have multiple dependencies on other stories or systems ● Requires a skill set or experience that not strong in the team ● Product owner might find it difficult to accurately describe the user story ● Multiple unknowns ● May need comparatively large scale of refactoring ● Requires significant research ● Requires highly experienced programmers with senior-level programming skills ● Requires somewhat difficult judgment calls ● Story implementation may have moderate impact external to the story itself 3 ● Complexity of moderate scale ● Moderate number of dependencies on other stories, systems, or subsystems ● Needs skill-set or experience that is reasonably strong in the team ● Product owner might have some difficulty describing details accurately ● Moderate level of unknowns ● Some refactoring may be required ● Needs intermediate programming skills to accomplish task ● Little research required ● Requires few important judgment calls ● Effects of the story have minimal impact external to the story itself 2 ● Technical and business requirements are easily understood ● Little or negligible research required ● Few unknowns ● Needs basic to intermediate level of programming skills ● Effects of the story are almost completely localised to the story itself 1 ● Very straightforward ● Crystal-clear technical and business requirements ● No unknowns ● No research required; jump directly at task ● Basic programming skills required ● Effects of the story are confined to the story itself Effort Value Guidelines 5 ● An extremely large story ● Too large to be estimated accurately ● A definite contender to be broken down into a set of smaller stories ● May be a candidate for separation into a new project 4 ● A very large story ● A longer focused period of effort may be required ● May take more than a week, even two weeks; should consider breaking it down into a set of smaller stories 3 ● A moderately large-sized story ● It can be something between two to five days of work 2 ● In a rough estimate, it may take a day or two of work 1 ● A very small story representing tiny effort level ● It may take a few hours of work C o m p l e x i t y 5 5 8 13 21 21 4 3/5 8 13 13 21 3 3 5 8 13 13 2 2 3/5 5 8 8 1 1 2 3 3/5 5 1 2 3 4 5