Digesting the problem
The problem the application will be designed to solve has been defined. Speaker Meet will bring technology speakers, communities, and conferences together. Now that the purpose has been defined, it must be digested.
As was suggested before in a previous chapter, attacking a new application from all directions is ill-advised. It can be quite a daunting task to attempt to approach a new software project by implementing each and every desired feature all at once. It can also be a large chore to define every want and need of the system.
It would be far better to define small, manageable chunks of the application that can be delivered quickly in order to evaluate their correctness and effectiveness. The trouble is, how does one define what can be separated into small pieces and determine that this small piece is of sufficient value?
Epics, features, and stories; oh my!
Many software development projects will maintain what is referred to as a product backlog. This is where everything...
