is it a good idea to include source safe binding information in solution and project file?

Microsoft is, as usual, kind enough to give yet another headache to the development team when they gave TFS. I bet its just copy paste from VSS code. (After all both sucks equally)

What I don't like about both of them is the fact that they uses .net solution file and project file to keep track of these binding information.
Now even if I agree that microsoft was kind enough to give those .sln and .csproj file, that doesn't give them luxury of using those file for whatever they think would be OK.
Now when I am working in integrated VS environment, my .sln and .csproj file has many reason to change and I end up, checking then in every single time. And of course, those .vsssc and what not are all your friends. Every single time when you what to check in, this extra noise is always present.

Dam it!!!! Microsoft sucks....

Why can't I have something like subversion. You better keep track of your binding stuffs separately. Give me subversion and I am happy on any day. But never VSS or TFS

I have been fighting on my current project to see if we can change source control. But the real problem is client has standard across all projects to use TFS. (Some people are blind follower of MS)

So best of luck to me again!!!!!!!!
I am hopping to make difference here.

why would you use scrum?

So far I have seen many reason for why an organization should start doing scrum over waterfall.
They all ultimately nail down to some of these:

• Frustration
• Not able to meet deadline
• Increased stress towards the end of the project.
• Software with nice to have features but has almost nil business value.
• Historical failure in the project

3 days back I have started with my new assignment and was very excited for working for one of the big B in the industry. Again from what I learned from job description and then during the interview process,was promising too.

Now since I am insider here, I know some of the ground reality. Here is the few comments that I heard on very first day, as reason for choosing scrum methodology for my current project.

• This project was in planning phase since last 18 month and we never had something concrete which can be shown to upper management.
• No one know about project requirements and after searching little bit, we found scrum as the only methodology which allows us to work without requirement.
• We don't have any process or discipline and scrum is the only possible ad hoc way to do this

After hearing all this, it might sounds frustrating but the silver light here is that: team is really interested in trying this new methodology and they do believe in making things done. People are open for trying new things and learning.

So here is what I am thinking of doing

• Introduce TDD and BDD(yes they aren't doing it either)
  
• Scrum training for team and upper management (session as well as on the job demonstration)
• Pairing with each member for getting them up to the speed (Playing red-green-refactor game)
• Re-structuring project solution and refactoring overall architecture.
• Introducing SRP, DI, IoC to the team.
• Start using structuremap, NAnt, MSTest, Resharper, RhinoMock

Well, best of luck Mahendra! Hope you can make difference.

finally, Jeffrey is the great guy. I owe all these learning to him, which I am going to implement here. Hey Jeff, its party time for you. Your teaching is paying off here :)