A,Limit scale of initial project ,Verifyable Requirements,Limited feedback from non-stakeholders,Existing Technical expertise,prioritize functionality,Work results validated,Low priority on quality for Proof of Concept,Organizing decision history not valuable in a chaotic context,Documentation of current work,Documentation of planned work,prioritize functionality,Documentation of finished work,Documentation of planned work,Documentation of planned work, Agile Development,Digital Kanban,Active communication with outside experts,Documentation of planned work,Co-location reduces need for organized communication,Flat management structure,Project manager role,Version control,38,36,18,Unit tests,Unit test,Clear responsibilities,Clear responsibilities,Verification of work,40,Concrete requirements known at start,Slack for project documentation,Functionality over testing,Post-mortem,One session validating requirements hypotheses,Minimized version of Scrum,Started with proof of concept,Kanban wall,Story points,Trello,Initial specific market segment perspective,In-house testing,Constant communication,Spaghetti-code excusable in a throw-away prototype,Weekly Scrum,Democratic decision of development environment,User stories,Strict project management considered a factor in project success,Planning Poker,Everything visible to all team members,Documentation of activities,Git Version Control,Functionality rather than UI,Categorized Slack channels,Jira considered hoo heavyweight for small team,Goal: Independent platform,Expert advice preventing some mistakes reduces need for testing,Development environment suits problem area,Limited Code Review,Council of advisors,Clearly visible project assignments,Walls documented digitally,Team proficient in development environment,Low priority on architecture,No unit testing for throw-away prototype,Quantitative initial requirement,Active communication within sub field,Communal working space
