Recent submissions

Comment · 9 years ago
Comment · 9 years ago
Comment · 9 years ago
You don't need to be a technical genius to start learning about the software development lifecycle. Any professional programmers you speak to will require some sort of business requirements. It is your responsibility, as the business owner, to outline the who/what/when/where of each feature (and leave the 'how' to the experts).

You also need to understand the impact of no defined scope. Typical business plans or MVP requirements will absolutely define a scope. This scope of work should match your best guess for a minimum viable product - based on your market research. This allows you to remain on budget and measure your success.

With a solid business plan, a set of strategic business requirements, a well defined scope, and 2x salary - you will have no problem finding talented developers.

Comment · 11 years ago
The key is to ensure every item on your board (hope you have a board) is actionable and deliverable by the end of your sprint. If a task is missing requirements or artifacts - move it back. If a task can not result it a fully tested and deployable piece of software - break it down.

And lastly, human beings suck at estimating time - base your first sprint on hours or timeframes and then move to a point based system.

Good luck

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton