So most companies i've been at say they are agile, but really aren't. I understand...it's hard to transition but I was put as the owner of the QA department in a small company and im really trying to get an actual process going.
So one thing that HAS worked is actually get a Kanban board system setup for Issue tracking. we've been linking MR's to issues and as they close they get pulled into retest (where I test them) and finally moved to close.
However the actual "start" of the development cycle is where this falls apart. Collecting requirements and so forth. I understand the "general" idea of how agile works but im really trying to understand in detail.
To "Me" what feels right is the following steps:
- New Project-->Statement of Work
- Requirements identified from SOW (Would require a BA or knowledgeable dev or COO or someone to list them out (How?) and then get signoffs from client.
- Estimation and Discovery phase (do story points get assigned in discovery phase? what about estimation)
- Using some system (Like Jira?) list all Story points
- Per Sprint (or weekly meeting) assign stories.
This helps me because I can test against stories and know exactly what to expect. But how on earth do you set this up against a client that is not used to this process. We've used basecamp before and it's just....messy?
I was just trying to get an idea if what I see is even remotely correct?