© 2017 by ScrumVanguard

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

C

  • Cadence - when development team attains sustainable or synchronous flow of work; meetings and consistent pace. 

  • Capacity - ability of the development team to complete work in relation to known and unknown variables, such as established team velocity, individual productivity frontier, holidays, planned and unplanned vacations, documentation, research, spikes etc.  

  • Card - disposable material for planning, conversing, tracking and holding user stories, spikes, defect and issues.  

  • Certification - qualification, credential and background showing suitability for the common purpose - as in Agile.

  • Changes - the activities performed to modify or resolve a problem.

  • Charter - mostly informal written point of reference helping the tester stay on track. (Unrelated to Project Charter). 

  • Chickens - mostly refers to stakeholders' role in Scrum, that is Scrum roles outside the Scrum Team.

  • Code structure - agreed form of code organization for clarity, intellectual management of program, module and function and interface in programming.

  • Colocation - having all product and project teams in one physical location, term is also used for data center facility.

  • Communication - an act of conveying mutually understood information using words, signs or meaningful symbols. 

  • Complexity - problem, complicated issue such as cyclomatic complexity measuring independent software paths.

  • Continuous Delivery (CD) - mode of sustained software shipment to users following consistent changes, new builds, or bug fixes happening in short cycles of 1-3days also called Agile cycle. A routine supported by deployment ready code.

  • Continuous deployment - marked by development changes via automation into production severally, diurnally.

  • Continuous Integration - building, testing and integrating code frequently at development pace, but short of deployment.

  • Courage - ability to speak up, be bold despite possibility of coercion.

  • Customer - a team of cross functional members, technical, business and political navigators representing the users of a product.

  • Customer review - XP practice suggested to allow customer review development items prior to "done." Exploratory review for validation of basic functionalities such as design layout, plain text content, terminology, field data and design elements, icons etc.   

  • Cross functionality - required skills (programming, testing, documentation, leadership) for end-to-end product development within  a development team, not the Scrum Team.

Return to forum to suggest new Agile words. Your suggestion will be reviewed and added if approved.