Project Dashboards [closed]
Closed 9 years ago.
How do you keep track of a requirements document on an agile team?
I understand that User Stories dominate the agile world, but how are these artifacts stored, so that new developers who join the team can come up to speed with the requirements?
Test driven vs Business requirements constant changing
One of the new requirement of our dev team set by the CTO/CIO is to become test driven development, however I don’t think the rest of the business is going to help because they have no sense of development life cycles, and requirements get changed all the time within a single sprint. Which gets me frustrated about wasting time writing 10 test cases and will become useless tomorrow.
Evaluating a product owner [closed]
Closed 8 years ago.
How do bug reports factor in to a sprint?
I’ve been reading up on Scrum recently. From my understanding, a meeting is held before the sprint starts, to decide what gets moved from the product backlog to the upcoming sprint backlog. Once a feature is completed in the current sprint, it will go into the “Ready to QA” bucket, and it’s at this point that I’m getting confused. Do bug reports go back into the product backlog? I assume they can’t go back into the sprint backlog as we’ve already decided what work will be done for this cycle? What happens when QA finds a bug? Where does it go?
Link between tests and user stories
I have not see these links explicitly stated in the Agile literature I have read. So, I was wondering if this approach was correct: Let a story be defined as “In order to [RESULT], [ROLE] needs to [ACTION]” then
IEEE SRS documents: lightweight version when working with outside contractors?
Typically we follow an Agile development process that tends not to put an emphasis on writing requirements and technical documents that nobody will read. We tend to focus our limited manpower to development and testing activities with collaborative design and whiteboarding as a key focus.
Behavior-Driven Development / Use case diagram
Regarding growing of Behavior-Driven Development imposing acceptance testing, are use cases diagram useful or do they lead to an “over-documentation”?
How to implement Scrum in a company with three similar web-based products
I am somewhat familiar with the concepts and benefits of Scrum. With that in mind, I am trying to improve the failing Scrum product management structure of a company I’m now working for that has three separate B2C products, catering to the same demographic and accessible on the same website. Each product has a product owner and a unique development team (5 – 9 people in each) behind it.
Requesting quality analysis test cases up front of implementation/change
Recently I have been assigned to work on a major requirement that falls between a change request and an improvement. The previous implementation was done (badly) by a senior developer that left the company and did so without leaving a trace of documentation.
Here were my initial steps to approach this problem: