… à l'Ecole de la V.I.E …

Agile frequent verification and validation Any iteration in agile development must produce artefacts, typically code, that pass the phase of verification and validation. Therefore, all iterations must have phases like this. For requirements and design, the verification and validation is the result of peer reviews with team members and with the customer For coding, verification […]

Agile Continuous Integration   Continuous Integration is a software development practice where members of a team integrate their work frequently, usually each person integrates at least daily – leading to multiple integrations per day. Each integration is verified by an automated build (including test) to detect integration errors as quickly as possible. Many teams find […]

Agile technical debt and escaped defects Escaped Defects Escaped Defects are those defects reported by the Customer from production that have escaped all software quality processes are represented in this metric. Technical debt Technical debt is the amount of Escaping defects at a time. How proceed with Technical debt ? Escaping defects should then be […]

Agile cycle time and lead time Cycle time Cycle time clock starts when work begins on the request, and ends when the item is delivered. Cycle time is a more mechanical measure of process capability. Cycle time is the time between two successive deliveries. To improve Cycle Time Reduce Number of Things in Process Improve […]

Agile risk and spike Risk based spike : A spike solution, or spike, is a technical investigation. It’s a small experiment to research the answer to a problem. For example, a programmer might not know whether Java throws an exception on arithmetic overflow. A quick ten-minute spike will answer the question. Why use spike? Spikes, […]

Accounting for Agile Project Labor Costs In order to understand the capitalization of agile development expenditures, we should return to the definition of an “asset” and “capitalization,”. The three stages of an IT project can be applied to agile as well as waterfall-developed software projects. Accounting An asset is defined as a potential future economic […]

Agile project management vs Traditional project management Agile is a Different Philosophy Traditional project management : • Plan what you expect to happen • Enforce that what happens is the same as what is planned – Directive management – Control, control, control • Use change control to manage change – Change Control Board – Defect […]

Agile dictionary Adaptive – Frequently responding to changes and learning’s on a project by changing the plan, priorities, and/or approach. Agilists believe changes are good! Agile Methods – A set of development methodologies characterized by being iterative, adaptive to changes and learning, value driven, low ceremony, and encouraging empowered teams. BDUF – Big Design Up […]

Agile vendor management Vendor management approch The Agile Manifesto values customer collaboration over contract negotiation which sets an important tone for procurement relationships on agile projects. The Agile Manifesto sets forth the idea that a buyer and seller work together to create products and governs the entire procurement process. Determining need and selecting a vendor […]

Agile earned value management Variance and trend analysis Unlike traditional project management methods that evaluate risk and variance and trends in formal meetings, agile incorporates risk analysis and variance and trend analysis into iteration review meetings. Risk and variance and trend analysis may be performed in agile using information radiators, like a risk burndown chart, […]

Agile terminology (8) CAS A complex adaptive system, or CAS, is a system composed of interacting, adaptive agents or components. The term is used in agile to remind practitioners that the development of a product is adaptive in that previous interactions, events, decisions influence future behavior. The term chaordic (a made up word blending chaotic […]

Agile games / Innovation games The phrase innovation game refers to a form of primary market research developed by Luke Hohmann where customers play a set of directed games as a means of generating feedback about a product or service. The research is primary because the data collected is gathered directly from customers or prospects […]

Agile failure modes and alternatives The top 12 causes of agile failure (failure modes) according to Aaron Sanders: 1. A checkbook commitment doesn’t automatically cause organizational change or support. 2. Culture doesn’t support change. 3. Culture does not have retrospectives or performs them poorly. 4. Standards and quality are lost in a race to project […]

Agile terminology (7) Compliance (organization) Compliance with a company’s code of ethics and professional conduct is standard practice in agile. [PMI Agile Community of Practice Community Charter. Project Management Institute.] Control limits for Agile projects Control limits – those which set an objective range to indicate whether a process is controlled or stabilized or defect […]

Agile frameworks and methodologies FDD Feature driven development (FDD) uses a prescriptive model where the software development process is planned, managed, and tracked from the perspective of individual software features. FDD uses short iterations of two weeks or less to develop a set amount of features. The five step FDD process is: 1. Develop overall […]