I am working on a small product based company developing .Net applications. There is a small team with 5-6 developers. I am a person responsible for planning everything. But my primary role is Software developer.Now our current project is very unstable because of poor organization. Today my boss called me and told to submit a report about required resources, appropriate methodology, required man power and their salary scales to make the current project success.I know I dont have enough organization skills and I need to go deep in my programming skills. So I need to focus only in the development. So I cant manage the project anymore.Now I am searching some other ways to make ongoing development success. My questions areWhat is the suitable agile methodology to my team?Is Scrum is suitable for above mentioned scenario?If we adopt Scrum, what we have to do next? (I think hiring new oneto manage the project is more suitable. So we have to get Scrummaster and some other developers.)Are there any resources (books, Blogs and etc) to get some tips andadvices to solve this problem?If Scrum is not a suitable methodology for our scenario, what elsecan be more suitable methodology to adopt?Can anyone give a good solution for my problem?
How to adopt scrum agile methodology for a small .Net team
project management;agile;scrum;organization;development methodologies
Yes, scrum may very well be appropriate, but you need to learn more about it.  Ken Schwaber's book will tell you a lot of stuff--like how the Scrum Master is not at all a project manager, and that the team needs to be self-organizing.The main things you'll need if you're going down the agile route, is a team who can self-motivate and pick up whatever ball gets dropped in front of them, customers who are willing to work closely with the team throughout the development process, and a product owner who has the wherewithal to decide what needs to be within your current and longterm scope and its priority.  So, first you need to learn more about scrum and decide whether it is appropriate. If you so decide, you'll have to talk to all the stakeholders and see if they are willing to give it a go--hopefully one of them taking the reins as Product Owner.  Then you'll either need to hire or become a Scrum Master.