We are a small start-up that is growing fast.
We have 4 departments: (Backend dev [2 pers], Frontend dev [2 pers], QA [2 pers], and one system administrator)
Before using Scrum methodology, we didn't have a clear idea about our progress, what others are working on, etc. Now we passed this issue, but we face a big issue now; it seems that the team is not conformable with the current methodology.
To give you a clear view on our case, here is how we proceed to handle a project:
We have a backlog meeting with product owner. The team defines the release backlog in another meeting (basing it on priority set by the product owner) Each department slices the release backlog and lists all tasks needed to be done by the next sprint. For instance, the backend group will start working on an API, front end will deal with designers and get the ready templates ready, the QA team will read and understand stories, and system administrators need to define the next priority according to the current project.
Each department creates their own sprint. (It's weird I know :s) and in the end we have 5 sprints. (The 5th one is for business employers. Well, they want to be part of the methodology, lol.)
Before we start using Scrum, we were respecting a cycle of two weeks, and after implementing Scrum, the project manager suggest that sprints need be done in two weeks. However, we just found that a sprint may take more :s.
According to our case, I have a list of question coming to my head.
Do QA, Backend, Frontend, and System Administration fit in Scrum methodology? What can we do if QA and system administration has a daily tasks? Can we use just one Sprint instead of 5?