Save £12 Million every year > Save £3 Million every quarter   
The Big Agile Toolkit: no Dogma, no Bias, no Accreditation, no Exams & no Fees   
 Agile sucks  Agile sucks   Instant Agile   Instant Agile

Conclusion   »   Toolkit Glossary   »   Agile Glossary




This is the The Big Agile Toolkit Glossary.

  1. Agile Governance Gap:
    This is a summary of the hidden responsibilities and costs that naturally occur on ALL projects that Agile Projects do not identify, cover and manage.
    Top of Page   

  2. Agile Project Experience Measurement APEx:
    This is the technique used to identify and quantify the experience of an Agile team to deliver an Agile Project.
    Top of Page   

  3. Agile Project Pipeline:
    The Agile Project Pipeline is a set of projects in the organisation portfolio that can be executed by the organisation in a specified time.
    Top of Page   

  4. Assessment Deliverable:
    An assessment Deliverable is an output built and created within the project that will be used in an assessment by the business user or other assessment personnel. In our view there is no added benefit in, and therefore no need to create, something that is not going to be assessed by someone. It might be a screen, a report or document or something else from the project. It may be technical like encryption rules or performance data or website SEO statistics. Nevertheless it will be assessed by someone and we use the term to focus on the process that someone will assess it and, importantly, they assess it on the basis of a fit for purpose assessment which will return it to the project if it fails the assessment.
    Top of Page   

  5. Agile Transformation:
    An agile transformation is the controlled, structured, planned development and implementation of a change that delivers specific organisational and governance objectives by means of a project to translate an organisations project delivery environment and its personnel in a staged approach from an existing operating model to a target operating model (T.O.M.) while introducing appropriate techniques and repeatable processes that support the principles of the Agile Manifesto and that assist the delivery of projects to time, quality and to budget.
    Top of Page   

  6. Agile Testing:
    This is the process of examination of the partial or full solution performed on a project using modified and conventional examination methods inside an agile governance.
    Top of Page   

  7. Auditing Agile Projects:
    This is an examination of a project that is operating or purports to be operating in an agile manner.
    Top of Page   

  8. Backlog:
    The concept of the Backlog is a simple one and a long standing idea too. Simply put it is a list of things that the project will address. SCRUM has however expanded its own rules and added further complexity and yet more titles for these simple lists. SCRUM introduced the titles of The Product backlog and the sprint backlog. The Product backlog in SCRUM is the list of requirements the project wants to deliver. The sprint backlog is the list of tasks that the SCRUM team is committing on the project as part the sprint. It also introduces the artefact known as the Impediment Backlog. Not surprisingly this is a list of impediments. The impediments are the obstacles that are blocking or slowing down the progress of the project.
    The Big Agile Toolkit uses a simpler method, there is one list and it is called the Build and Fix List.
    Top of Page   

  9. Benefits Mining:
    This is the process to unearth and extract the benefits proposed on the project.
    Top of Page   

  10. Build and Fix:
    This is the process to perform development and defect repair of a solution on a project.
    Top of Page   

  11. Burndown Chart:
    This is a graph showing the remaining work outstanding against the elapsed time on a project.
    Top of Page   

  12. Commitment:
    AKA Engagement Commitment. There are a series of commitments entitled Engagement Commitments that define specific responsibilities, partnerships, collaborations and alliances of people on a project to share obligations to deliver these specified promises under genuine threat of project cancellation if a failure to commit to one of the Engagement Commitments on the project occurs.
    Top of Page   

  13. Commitment Failure:
    This is an event that takes place when a failure to commit to one of the Engagement Commitments on the project occurs.
    Top of Page   

  14. Continuous Integration:
    Continuous Integration is a technique used during the development of software solutions. It involves regularly submitting or committing of source code to a central code repository.
    Top of Page   

  15. CRAID Log:
    This is a log that includes Risks, Assumptions, Issues, Dependencies as well as constraints on the project.
    Top of Page   

  16. Daily Forum:
    This is a meeting conducted on the project for all project stakeholders to understand and share the status of the project.
    Top of Page   

  17. DELIVER:
    This is a Stage of the Lifecycle for The Big Agile Toolkit. It is stage number two.
    Top of Page   

  18. DELIVER Develop:
    This is a phase of the Lifecycle for The Big Agile Toolkit. It is phase number three inside stage number two.
    Top of Page   

  19. DELIVER Release:
    This is a phase of the Lifecycle for The Big Agile Toolkit. It is phase number four inside stage number two.
    Top of Page   

  20. DELIVER Run:
    This is a phase of the Lifecycle for The Big Agile Toolkit. It is phase number five inside stage number two.
    Top of Page   

  21. Disengagement Interval DI:
    This is an interval of 1 working day before a project is stopped and when all project resources are formally Disengaged if a project Engagement Commitment stays broken.
    Top of Page   

  22. First Fix Localisation:
    This is the process to perform Localisation on the processes of an organisation with a view to defining the refined processes as a result of an agile transformation and is specifically reached when a set of combined best practise processes are established and incorporated successfully within the stages and phases of the Lifecycle.
    Top of Page   

  23. Governance GRID:
    GRID is the mnemonic we use in The Big Agile Toolkit to represent the four main elements we consider when we apply governance to agile projects.
    Top of Page   

  24. Impediments:
    Impediments are the blockers or obstacles that are interrupting or slowing down the progress of the project. They are identified in the assessments, in reviews and in retrospectives. The changes go into the RAID Log to determine if they need work and into the Build and Fix list if they need building or fixing.
    Top of Page   

  25. Iterative Modelling:
    Iterative Modelling is a technique used to build, present, adjust and re-present models and early prototyped options for a project to illustrate, broaden and confirm its understanding of a requirement or a possible solution.
    Top of Page   

  26. Lifecycle Localisation:
    This is the process to perform First Fix, Second Fix and Third Fix Localisation on the processes of an organisation with a view to defining the refined processes as a result of an agile transformation.
    Top of Page   

  27. Macro Customer Liaison - MaCL :
    The process to communicate the status and issues surrounding the wider programme and alignment to major business objectives and strategy with senior business personnel.
    Top of Page   

  28. Micro Customer Liaison - MiCL :
    The process to assess and communicate a meticulous appraisal of fine granular data and processes involved in delivering the end-to-end solutions and day to day issues regarding people and deliverables.
    Top of Page   

  29. Minimum Acceptable Delivery:
    The Minimum Acceptable Delivery (MAD) is the smallest amount of usable functionality that you will accept as a working solution and that you can work with.
    Top of Page   

  30. Operating Model:
    This is the definition of the operational processes as controlled by your management which result in the production of your output.
    Top of Page   

  31. Organisational Models CHIMP:
    These are the five organisational elements considered as part of organisational definition and planning. They are identified by the mnemonic: CHIMP.
    Top of Page   

  32. Pair Programming:
    Claimed as an agile technique, pair programming is an engineering technique and an old one too. My own grandfather, a Dads Army ARP in World War II, loved the phrase two heads are better than one. This refers to the same idea that a problem is best faced with the support of a colleague, it allows a different perspective to be introduced and presents an opportunity to have your assumptions challenged, reviewed and tested.
    Top of Page   

  33. Project Disengagement:
    This is a process that is performed when a failure to commit to one of the Engagement Commitments on the project signals the cancellation of the project.
    Top of Page   

  34. Project Selection:
    This is a technique with four important elements or selection parameters used to select pathfinder or candidate agile projects.
    Top of Page   

  35. Project Selection Parameters : CASC:
    These are the four elements (aka selection parameters0 used to identify and select pathfinder or candidate agile projects.
    Top of Page   

  36. Projectivity:
    Projectivity is the measure of your organisational agile project performance.
    Top of Page   

  37. Projectivity Index:
    The Projectivity index is the benchmark to use to compare your organisational agile project performance with other organisations, across projects and across time.
    Top of Page   

  38. PseudoSuccessusAgileProjectivitism :
    The ideology to seek to covertly compare projectivity success across unlike agile projects.
    (Guinness Book of Records submission for Longest unchallenged nontechnical word in publication).
    Top of Page   

  39. PUSH User Group:
    These are the four types of users to anticipate on the project.
    Top of Page   

  40. RACI Matrix:
    This is a technique to group the various role types that individuals play on the project.
    Top of Page   

  41. RAG Status:
    The RAG status is the relative status of the project as represented by a colour to identify the relative criticality of the projects delivery stability and risk profile.
    Top of Page   

  42. RAID Log:
    This is a log that includes Risks, Assumptions, Issues, Dependencies on the project.
    Top of Page   

  43. Readiness Quotient:
    A Readiness Quotient is the post assessment numeric that is used to compare against the Target Readiness Quotient.
    Top of Page   

  44. Readiness Statement:
    A Readiness Statement is one of the assessment explanations made as part of the Readiness Declaration when assessing the project landscape.
    Top of Page   

  45. Rightshifting:
    The progression to improve organisational capability to achieve strategic goals and deliver customers desired outcomes and expected benefits by delivering required quality at a required time at an required price.
    Top of Page   

  46. RIP Graph:
    A RIP Graph is a visual technique used to represent and map risks impact and probability.
    Top of Page   

  47. Second Fix Localisation:
    This is the process to perform Localisation on the processes of an organisation with a view to defining the refined processes as a result of an agile transformation and is specifically reached when the Agile Transformation Capability Threshold is reached and breached successfully.
    Top of Page   

  48. SeSiSNo:
    This is the mnemonic for the four statuses of emergency incident reporting the Business Impact of an emergency incident error including Severe, Sizeable, Small and None.
    Top of Page   

  49. SETUP:
    This is a Stage of the Lifecycle for The Big Agile Toolkit. It is stage number one.
    Top of Page   

  50. SETUP Define:
    This is a phase of the Lifecycle for The Big Agile Toolkit. It is phase number one inside stage number one.
    Top of Page   

  51. SETUP Survey:
    This is a phase of the Lifecycle for The Big Agile Toolkit. It is phase number two inside stage number one.
    Top of Page   

  52. Scope Cheap:
    This is a scope management technique in The Big Agile Toolkit which takes advantage of the practice or opportunity to get extra functionality for free.
    Top of Page   

  53. Scope Creep:
    This is a scope management phenomenon in The Big Agile Toolkit whereby the scope of a project is enlarging and deviating without apparent control and evaluation.
    Top of Page   

  54. Scope Reap:
    This is a scope management technique in The Big Agile Toolkit which takes advantage of estimating cautiousness.
    Top of Page   

  55. Scope Seep:
    This is a scope management technique in The Big Agile Toolkit that demands a project will experience and demonstrate an equal and instant adjustment of scope to mirror any scope adjustment.
    Top of Page   

  56. Small Change Process:
    This is a fastpath technique to deliver small changes within The Big Agile Toolkit.
    Top of Page   

  57. Solution Assessment:
    AKA Assessment. This is an evaluation of part or all of a solution performed by the project team to determine if the element of the solution is acceptable and fit for purpose.
    Top of Page   

  58. Spike:
    Agile Spike is a technique that performs a single test to evaluate and confirm (or challenge) a story or section of a solution.
    Top of Page   

  59. Technical Debt:
    This is a contemporary tag line to describe the leftover remains and circumstances that linger and which an organisation are left to ponder (and repair) after a period of careless or hurried development.
    Top of Page   

  60. Tracer:
    Agile Tracer is a technique used in prototyping as part of product development and is performed periodically to ensure the proposed outcome is aiming towards its target objectives and target solution.
    Top of Page   

  61. Transformation Failure:
    These are the five circumstances where Agile Transformation may fail to deliver the planned transformation outcomes.
    Top of Page   

  62. Transformation Capacity Threshold:
    This is the essential number of projects to be put through agile transformation before an agile transformation is robustly declared as delivering planned transformation outcomes.
    Top of Page   

  63. Third Fix Localisation:
    This is the process to perform Localisation on the processes of an organisation with a view to defining the refined processes as a result of an agile transformation and is specifically reached when the Agile Transformation Capability Threshold is reached and breached successfully.
    Top of Page   

  64. Velocity:
    Velocity is a method for measurably demonstrating the rate at which a project develops software and delivers business value. It is calculated by deriving the number of user stories that the project delivers in each timebox (or sprint).
    Top of Page   

  65. WHERE Test:
    This is the Wide Huge Eyes Raised Eyebrow Test and is an evaluation of an estimate to determine if it is of the order of estimate you, or a professional estimator, would expect.
    Top of Page   



Buffer



 Agile sucks     Agile sucks   Instant Agile    Instant Agile



Glossary:     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


#personas  »   #artefacts  »   #archetypes  »   #patterns  »   #change  »   #personas  »   #increasingoutput  »   #reducingvariation  »   #improveefficiency  »   #abstraction  »   #predictionandcontrol  »   #management  »   #organisations  »   #socialnetworktheory  »   #failfast  »   #quality  »   #waste  »   #complexity  »   #learning  »   #adapt  »   #inspect  »   #improvement  »   #models  »   #complexadaptivesystems  »   #informationflow  »   #sytemsthinking  »   #butterflyeffect  »   #unpredictability  »   #chaos  »   #emergence  »   #emergentbehaviour  »   #distributedcontrol  »   #continuousimprovement  »   #complexityscience  »   #gametheory  »  
 Agile In 6 Steps    |    Projectivity    |    Instant Agile    |    Risks    |    Auditing Agile Projects 
Big Agile Toolkit Book (Amazon Japan)   |   Big Agile Toolkit Book (Barnes and Noble)
Buy the Big Agile Toolkit Book   |   Buy the Big Agile Toolkit Kindle eBook
Agile Glossary






   


The Big Agile Toolkit

 SPADE: Successful Pragmatic Agile Delivery Everytime™ 
   
Topic: 439  Page: 441/444  Progress: 99.3%
 About    |    Author 
Follow @BigAgileToolkit


This content can be copied to third parties for personal use if you acknowledge the source of the material with website URL (http://www.bigagiletoolkit.com/) and Twitter hashtag (#BigAgileToolkit).
In all other cases, no part of bigagiletoolkit or associated text or website may be copied reproduced or redistributed in any form or by any means without prior permission in writing from the author.
Agile Project Governance for Cost Conscious Companies™

All rights reserved.