,A,B,C,D,E,F,G,H,I,Low priority on quality for Proof of Concept,Verifyable Requirements, Agile Development,Organizing decision history not valuable in a chaotic context,Existing Technical expertise,Documentation of planned work,Documentation of current work,Documentation of finished work,Limited feedback from non-stakeholders,Limit scale of initial project ,Project manager role,Co-location reduces need for organized communication,Flat management structure,Active communication with outside experts,Version control,Internal verification of work,Digital Kanban,prioritize functionality,Requirements elicited and analysed,Later complications excusable for results now,Expertise internalized within team,Lean development,Project manager role,Agile development,Project owner role,Documentation of current work and short term plan,Priority on quality of data layer,Version control,Product tested by customer in development,Early customers reduce uncertainty,No technical/business model need for a prototype,Design & practices support independent work methods,Low technical uncertainty,Clear responsibilities,Oversight of current and near-future work,Chaotic context,Iterative development,Limit overhead,Co-location reduces need for organized communication,Flat management structure,Existing expertise leading to quick results,Not Agile development,Manual testing,Version control as documentation tool,Online chat service as documentation tool,Limit scale of initial project,Proof of concept,Documentation as a side product,Digital Kanban,Project is not of limited scope,Access to outside expertise,Trello downsides,Defined goals for project,Application expertise within team,Requirement analysis,Access to end-user,Manager role,Hack-and-Plan,Lean Development,Clear team member responsibilities,Test Driven Development,self-imposed deadline,Agile development,Digital Kanban,Verifiable requirements,Iterative development,Priority on user experience in testing,Rough requirements,Interfaces specified and tested manually,Organized coding practices,Behaviour Driven Development,Adaptable work procedures,Priority pon speed of delivery versus product quality,Team-building to increase effectiveness,Co-location reduces need for organized communication,Priority on product quality versus speed of delivery ,Version control as documentation tool,High level task definition due to chaotic context,Google Ventures Design Sprints,Version control,Google Docs,Version control,Design & practices support independent work methods,Digital kanban for requirements documentation,Decision of speed rather than quality,Clear division of responsibilities,Informal project management,Software architect role,Low maintainability,Manual testing,Agile development,New fitting framework,Software design for independent work,Lean Development,Self-imposed deadline,Low coupling,Whiteboard task management,Internal verification of work,High level digital kanban,Iterative development,Little work management,Vision basis for requirements,Agile development,Effective tools rather than speed,Effective cowboy programming,Unintended proof of concept,Low maintainability,Haphazard user testing,Manual testing,Cowboy programming,Informal user testing,Manual testing,Iterative development,Unit tests,Light-weight software design,Continuous development,Agile Development,Digital task tracking,Homogenized code,Clear responsibilities,Adaptable work procedures,Minimal low-level project management,Documented project plan,Self-imposed deadlines,Wiki as a documentation tool,Version control as documentation tool,Speed rather than correct development tools,Need for solution already validated,Iterative Development,Beta tests,Development environment minimizes weaknesses,Clear division of responsibilities,Document management unnecessary,Software architecture to support independent work,Speed rather than maintainability and scalability,Agile Development,Minimal low-level project management,Focus on visual designs,Frequent user testing,No documentation of requirements,No need for a formal communication system,Manual testing,Self imposed deadlines,Minimize cost of scrapping work,Iterative Development,Management role,Manual testing,Informal work management,Trello negative,Lack of deadlines,Group decision making,Design patterns to increase maintainability,Low priority on maintainability,Agile Development,No oversight on quality,Low technological innovation,Digital kanban,Pair programming,Project manager role,Self-imposed deadlines,Documentation as a side product,Lack of deadlines,Clear responsibilities,Deadlines,Existing expertise vs. new tools,Existing expertise,New tools,Proper tools,Existing expertise,Existing expertise,20,16,15,32,18,12,18,17,15,Unit tests,Clear responsibilities,Context,Tools,Policies,Practices,Feedback/Statements,Informal communication,Formal Communication,Communication,Validation & Verification,Documented requirements ,User testing: How and how frequent?,Expert advice,Unit tests,Manual testing,Work verification
