Test planning for an Agile sprint
Can anyone offer any tips or experience on developing a test plan for an Agile sprint? Most of the time our team simply creates a “Test Feature X” task and goes about writing ad-hoc test cases. There typically isn’t much strategic forethought put into how features will be tested and how we’ll communicate the expectations and results to the rest of the development team and our users.
How to start a development project when there are too many potential stakeholders
I’ve just taken on a new job at a college as (the sole) Web application developer.
Scrum: What to do with epics once the stories are clear?
When working on a backlog, you define epics and break them down into user stories. Epics are estimated and kept on the backlog as epics until they become important enough to be planned into one of the next sprints.
Do your stories include tasks across disciplines? How do you do capacity planning?
My organization does web projects and employs a handful of disciplines like backend dev, frontend, BA, UX, graphic design, QA. We’ve been pushing to have tasks for every discipline in our sprints with explicit dependencies (Can’t build a page without comps, can’t do comps without wires, etc). I’ve heard some other organizations say that scrum is only for dev tasks. Are we barking up the wrong tree? And, if not, are there any good tools for doing capacity planning when only certain resources can do certain tasks?
Splitting user stories into smaller stories
I’ve been reading various techniques for splitting large user stories in helpful ways, such as by user workflow through the system etc. What I’m struggling with is how to word these smaller stories if all they achieve is facilitating the next step in the process and not delivering the application’s main benefit to the user.
Is the following diagrams correct for RAD and Agile methodologies?
I do not know if this would be the right stack exchange site to ask this question but I have been researching on RAD (Rapid Application Development) and Agile methodologies and was trying to find their diagrams but if I google images this, it comes up with many different diagrams. So based on the images I drew my own diagrams on this.
How to deal with user interface design and respective feature support in Agile development?
In an Agile development process usually the main focus is on User stories, but sometimes a single requirement may span several user stories.
How to time the sprints in Scrum to allocate time for TDD?
We have sprints of 4 weeks duration. What I have been doing is 3 weeks dev time and 1 week of pure manual/automated testing, stabilization and shipment assurance testing.
Agile: When to re-factor and when to extend while accruing technical debt? [duplicate]
This question already has answers here: Rule of thumb for cost vs. savings for code re-use [duplicate] (7 answers) Agile estimation with tech-debt (3 answers) Closed 11 years ago. Consider the following scenario. You currently have a feature set A you wish to extend to include feature set B. In the near feature there’s a […]
Understanding the meaning of “multiple lifecycles application development”?
Some Agile job posts have a requirement “strong understanding of multiple lifecycles application development”, what does it means ?