inception
Scrum is an agile way to manage a project, usually software development. The primary artifact in Scrum development is, of course, the product itself. The Scrum model expects the team to bring the product or system to a potentially shippable state at the end of each Scrum sprint.
Within agile development, Scrum teams are supported by two specific roles:
The first is a ScrumMaster, who can be thought of as a coach for the team, helping team members use the Scrum process to perform at the highest level. We will chose the most expert in the technology that we will use.
**The product owner (PO) **is the other role, and in Scrum software development, represents the business, customers or users, and guides the team toward building the right product. We will choose the student who is the most frequently customer in resturants to represent the product owner.
We use a hybrid of waterfall and Scrum processes, but this is only because the course team forced us. In reallife we are hackers who don't need all of that :-)
- Chose a restaurant. (nice to have)
- Order a table. (mandatory)
- order a dose from the menu (mandatory) – enable options:
a. First courses
b. Middle / Main courses
c. Kids courses
- Order a dose from business menu
- Order deserts (mandatory)
- Order drinks (mandatory)
- Call a waiter (mandatory)
- Checkin (mandatory)
Note: because our planning can be complex, we won’t do the features that defined as nice to have. If we'll have the time, we will do it at the end.
- Build a mockup and main processes.
- Divide roles
- Build application using - 3 design model
- Check bugs
- Deployments and version control
Note: we need to reorganize the initial planning by scrum methodology
| Risk | Severity | Response | |
|---|---|---|---|
| 1 | incorrect division between the developers |
Medium | To perform an intelligent division. (will be the scrum master according to the scrum methodology) |
| 2 | Security payment through the app | High | the payment will be made directly with the waiter |
| 3 | Outdated information of a list of restaurants, menus and prices |
Medium | Frequently updating the list of restaurants, menus and prices |
| 4 | Dynamic and frequently changes in uses tables. | Medium | Get this data by resturant service |
| 5 | Too much capacity – The project may be completed after the required time | Medium | Minimized the mandatory capacity. The features rated as mandatory / nice to have |
Using css, html ,javascript for client side Using ASP.Net with MVC technology for server side Converting to ios / android.
We used Google App Engine because it's easy to create, easy to maintain, and easy to scale as our traffic and data storage needs change. With App Engine, there are no servers to maintain. We simply upload our application and it’s ready to go.
The Git feature that really makes it stand apart from nearly every other SCM out there is its branching model.
Git allows and encourages to have multiple local branches that can be entirely independent of each other. The creation, merging, and deletion of those lines of development takes seconds.
