# Feature Many project management tools — like Jira — were initially designed as bug trackers, interactive spreadsheets for bugs, whereas product requirements were created in Waterfall-style specs. Kanban boards were a later addition, inspired by manufacturing practices from Toyota car production. IF Method flips this logic. It was not conceived as a bug tracker, it was designed to be feature builder. Every card represents a feature iteration, and any defects — seen as technical damage — are assigned directly to the iteration where they originated. Unlike Kanban tickets, often treated like disposable napkins, feature iterations in IF Method are permanent fixtures. It’s in everyone’s best interest to keep them as engaging and useful as an actual book. The “Shape Up” approach by Jason Fried and DHH emphasises the importance of writing skills in software teams. IF Method also needs and hones this skill: the team should care for the Productbase just as meticulously as they \[should] do the codebase. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://handbook.swinlanes.com/main-concepts/feature.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.