Wednesday, April 1, 2020

cst438 Software Engineering

what does SMART mean in the context of requirements?

 User stories should be specific, measurable, achievable, relevant and timeboxed. Specific, user stories should not be vague. User stories should be measurable so they can be testable using numbers as criteria. They should also be achievable, so the user story should be finished in one implementation. User stories should have business value to one or more stakeholders using the 5 whys to find more stakeholders. Timeboxing means stopping work on a story when the time budget is up, then giving up or dividing the user story into smaller ones and then rescheduling those for the next iteration. One can also go to the customer to find the highest value story and doing that. 
at

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)

cst 499 week 8

This week, we finished writing the paper in order to do the best job possible even if it was a little bit late. Now that everything is done,...

  • Week 5 CST 311: Intro to Networks
    In Chapter 4, we learned about the Network Layer (the Data Plane). The topics covered: What’s inside a router, IPv4 datagram format and ad...
  • cst 325 w3
    This week, we learned how vectors and matrices are connected. We also learned how matrices are used to manipulate space and how to solve p...
  • CST 311 W 7
    This week, we learned about the link layer, error detection and correction, MAC protocols, and LANs and switches. In chapter 8, we learned...