Scrum and Technical Practices : Spikes, estimation and time-boxing
by Spike definition A spike is an investment to make the story estimable or schedule-able. A spike is a product development method originating from Extreme Programming …
Tag: Scrum testing
Scrum and Technical Practices : Technical Spike
Technical Spike definition Evaluation of technical elements for a proposed solution is a technical Spike. Technical Spike purpose A technical Spike may be used for …
Scrum and Technical Practices : Functional Spike
Functional Spike definition Mockups and wireframes are a spike however can be categorized under Functional Spikes. Functional spikes are often best evaluated through some level …
Scrum and Technical Practices : Architectural Spike
Architectural Spike definition A Spike is a quick and dirty implementation, a prototype that will be thrown away. Architectural Spike purpose An architectural Spike is …
Scrum and Technical Practices : Version Control, Branching, Merging and Standards
Version Control definition Version control (also known as revision control or source control) is a category of processes and tools designed to keep track of …
Scrum and Technical practices : Technical Debt
Technical Debt definition Technical Debt is the typically unpredictable overhead of maintaining the product, often caused by less than ideal design decisions, contributing to the …
Scrum and Technical Practices : Debt
Bug discovery purpose Bugs create Debt Debt types Incremental Debt : Caused by repeating the above without any work to reduce the debt Inadvertent debt: …
Scrum and Technical Practices : Bug Report
Bug Report purpose A bug report “should explain how exactly the product is broken.” Bug Report essentials There Key essential for every bug report are …
Scrum and Technical Practices : Bugs
Bug definition A software bug is an error, flaw, failure, or fault that produces an incorrect or unexpected result. Bug discovery purpose Bugs create Debt …
Scrum and Technical Practices : Testing, bugs and debt
Testing purpose Testing is considered a good agile development practice to think through requirements before writing functional code : It helps to consider work in …