Agile development teams are cross-functionally diverse and sufficient. They are comprised of team members that collectively have the skills to get the job done. But how do teams deal with the variability of the work they are asked to do from sprint to sprint? For example, what…
abstraction-hierarchy acceptance-criteria adaptation agile adoption agile-principles agile-transition antifragile antifragility approach batch-size benefits binning capital-expenditure capitalizing change chickens coaching component-team conditions-of-satisfaction continuous-delivery cost-accounting cost-of-change cost-of-delay crossing the chasm csm csp cspo daily-scrum daily-stand-up defect definition-of-done definition-of-ready development-team distributed-teams documentation done done-done economically-sensible epic essential-scrum estimating estimation external-stakeholders extrinsic_motivation fast-feedback feature feature-team firmware fixed-date-release fixed-scope-release fragile glossary government grooming group hardware idle-work idle-workers impediment innovation-accounting inspect-and-adapt internal-stakeholders intrinsic_motivation intuition invest joy keynote learning-loop marginal-economics metaphor metric minimum-marketable-feature minimum-releasable-features minimum-viable-product misalignment mmfs mrfs musketeer-attitude mvp naive-technical-debt negative-covariance nonfunctional-requirement operational-expense outcome-measure output-measure pbi pigs planning planning-poker point-inflation portfolio-backlog portfolio-planning potentially-shippable-product-increment practice prediction principle principle-of-least-astonishment product-backlog product-backlog-item product-owner project quality-template regulated relative-size-measure release-planning risk risk management safety scaling scrum scrum-framework scrum-role scrummaster sprint sprint map sprint-backlog sprint-execution sprint-goal sprint-planning sprint-retrospective sprint-review stacked-ranking stakeholder strategic-technical-debt sustainable-pace swarming t-shaped-skills task team technical-debt technical-practices theme timebox timeboxing transparency u-curve unavoidable-technical-debt uncertainty universities user-role user-story value-chain variability visual agilexicon wip
Blog Posts Tagged “t-shaped-skills”
How do you measure the performance of a development team? Should we use velocity? NO! Then what should we use? This blog proposes a set of five measures that you should consider when measuring the performance of your development teams.