Yes, the problem I always find is that everyone just talks about ‘a’ big project or a few with multiple teams. Where I was previously working we had numerous projects and one singe team. Because there was no development process in place, scrum seemed ideal. And as you the rightly pointed out, the team and company would need to change in order to fit scrum in. Whilst implementing scrum there were two key things that I done in order to start the transition into scrum:

1. Initially stay clear of jargon like ‘sprints’, ‘retrospectives’ until the stake holders have educated. A lot of people don’t like change especially when your using words that they don’t quiet understand.

2. Don’t just suddenly implement the whole of scrum. What you want to do is look at key area’s where improvements are needed. And implement scrum into those parts. For example, introducing a prioritized ‘backlog’ of tasks ‘not user stories ’ so that all the stake holders can see what work is required. And then possibly release planning or retrospectives etc.

It can be an uphill struggle, but you have a very good challenge there so don’t give up!

I have posted something on a LinkedIn discussion board – would be great to have your thoughts on there too. See http://www.linkedin.com/groupAnswers?viewQuestionAndAnswers=&gid=52030&discussionID=8703983&sik=1256822798414&trk=ug_qa_q&goback=.ana_52030_1256822798414_3_1