- Anonymous types must always have an initial assignment and it can’t be null because the type is inferred and fixed to the initializer.
- can be used with simple or complex types
- can be used as initializers in for loops
- can be used and has to be used for array initializers
- can be used with arrays
- can be returned from methods but must be cast to object
- cannot be used for a class field
I like user stories a lot. They help everyone talk the same language and results in a better product. User story alone does not constitute product requirement. User story is supposed to be a place holder for discussion which should happen between the team, Product Owner and the customer. This discussion result in a common understanding which along with the user story content is the product requirement. This format captures the essence of requirement without confusing the readers User Story is only one of the many different ways in which requirements can be represented. This is not mandatory in any Agile “process”. But many have made this mandatory. I have seen many spending countless hours trying to write the requirements in user story format when they could have easily written that in simple one-line sentence in few minutes. I have seen team members refusing to even discuss the requirement until product owner rewrote the requirement in user story format. ...
Comments