REUBEN CASTROL | Portfolio & Blog

We invest in Australians with big ideas who want to be the best in the world. We provide equity capital for Seed, Series A and later stage. No cheque is too early. We're committed to the development of our community and the strengthening of the Australian startup ecosystem.   Find out more . Home | Blackbird Ventures

Facebook failing, Zuckerberg and Sandberg absent: Commentary

The sprint backlog is a list of tasks identified by the Scrum team to be completed during the Scrum sprint. During the sprint planning meeting, the team selects some number of product backlog items, usually in the form of user stories, and identifies the tasks necessary to complete each user story. Most teams also estimate how many hours each task will take someone on the team to complete. It's critical that the team selects the items and size of the sprint backlog. Because they are the people committing to completing the tasks, they must be the people to choose what they are committing to during the Scrum sprint. The sprint backlog is commonly maintained as a spreadsheet, but it is also possible to use your defect tracking system or any of a number of software products designed specifically for Scrum or agile. An example of a sprint backlog in a spreadsheet looks like this: During the Scrum sprint, team members are expected to update the sprint backl

In the simplest definition the Scrum Product Backlog is simply a list of all things that needs to be done within the project. It replaces the traditional requirements specification artifacts. These items can have a technical nature or can be user-centric e.g. in the form of user stories. The owner of the Scrum Product Backlog is the Scrum Product Owner. The Scrum Master, the Scrum Team and other Stakeholders contribute it to have a broad and complete To-Do list. Working with a Scrum Product Backlog does not mean that the Scrum Team is not allowed to create and use other artifacts. Examples for additional artifacts could be a summary of the various user roles, workflow descriptions, user interface guidelines, storyboards, or user interface prototypes. However, these artifacts do not replace the Scrum Product Backlog but complement and detail its content. The Scrum Product Owner uses the Scrum Product Backlog during the Sprint Planning Meeting to describe the

Minimum viable product - Wikipedia : A minimum viable product (MVP) is a product with just enough features to satisfy early customers, and to provide feedback for future product development.[1][2] Gathering insights from an MVP is often less expensive than developing a product with more features, which increase costs and risk if the product fails, for example, due to incorrect assumptions. The term was coined and defined by Frank Robinson about 2001,[3] and popularized by Steve Blank, and Eric Ries.[4][5][6][7] It may also involve carrying out market analysis beforehand.

Ever had that feeling of not knowing where to start? For writers, it’s called  writer’s block. Painters call it  blank-canvas syndrome . Entrepreneurs refer to this phenomenon as  analysis paralysis , an affliction all founders experience at one point or another. It’s like having a stroke of genius for the next big idea, but not knowing where to start. Related:  Your Product May Be Minimal, But Is It Viable? Whether yours is a big marketing idea with the potential to double your holiday sales, the way Zappos did with its recent  price-matching  experiment, or the next billion dollar business, your idea -- and everyone else's -- are only as good as the execution behind them. Source: 6 Tangible Steps to Launch an MVP Product :