--- title: "More discussion about MS and agile methodologies" url: "https://osherove.com/blog/2004/6/4/more-discussion-about-ms-and-agile-methodologies.md" canonical: "https://osherove.com/blog/2004/6/4/more-discussion-about-ms-and-agile-methodologies.html" published: "2004-06-04T07:07:00" updated: "2004-06-04T07:07:00" tags: [".Net Original"] author: "Roy Osherove" description: "This post is a retort to this: http://geekswithblogs.net/jglynn/archive/2004/05/10/4751.aspx Jay hopes that my comments about adopting XP at Microsoft will never be heard. My answer to that would be hopefully never. In…" usage: "Licensed under CC BY 4.0 — reuse, quote and adapt with attribution (Roy Osherove, link to the original page)." license: "https://creativecommons.org/licenses/by/4.0/" --- # More discussion about MS and agile methodologies By Roy Osherove June 4, 2004 In [.Net Original](https://osherove.com/blog/category/net-original) **Historical article** · Originally published June 4, 2004; technical details may be outdated. This post is a  retort to this: [http://geekswithblogs.net/jglynn/archive/2004/05/10/4751.aspx](http://geekswithblogs.net/jglynn/archive/2004/05/10/4751.aspx)  Jay hopes that my [comments](http://weblogs.asp.net/rosherove/archive/2004/05/08/128219.aspx) about adopting XP at Microsoft will never be heard. _My answer to that would be hopefully never. In his post, Roy ponders how the XP process would work on projects as large and vast as what Microsoft produces. Is he really serious? Can something like Word be developed using XP?  I can't possibly see how._ Well, Jay , XP has worked on a **very** large project [over at Chrysler](http://www.xprogramming.com/Practices/xpractices.htm) a few years back (many years back actually). There's no reason to think that due process will not lead to success on even bigger ones. It's been working on many a projects around the world and for the past couple of years has been gaining more and more recognition as something that's definitely worth looking at and learning from. I myself have found that even taking \*some\* of the concepts it uses provides for huge benefits. And you know what? I'm sure MS is doing Unit testing somewhere behind the iron curtain. Granted, it's not as “evolved” yet, but its definitely something every good developer will want to know about. And MS is filled with those. More from Jay: _Microsoft needs to stay out of this area. They are best suited at making tools._ Making tools? how about Operating systems? programming languages? _I think it would become very difficult if Microsoft started shoving processes down my throat._ What have you been programming with so far in your N-tier applications? a few words: DNA, MSF, and parts of those are all in most of the development methodologies and architectures existing today. Like it or not. _And heaven forbid that they should start tieing features of the tools with processes._ Hardly. Tyeing in and facilitating certain abilities are two separate things. You won't **have** to do XP on Whidbey, but you **could** much easier than in previous versions. ## More in .Net Original [All posts in .Net Original](https://osherove.com/blog/category/net-original) - Jun 4, 2004 ### [Solving weird problems, and making others solve them as well](https://osherove.com/blog/2004/6/4/solving-weird-problems-and-making-others-solve-them-as-well.html) - Jun 4, 2004 ### [Planning a daily, automatic build](https://osherove.com/blog/2004/6/4/planning-a-daily-automatic-build.html) - Jun 4, 2004 ### [Managed Smart Documents Wrapper](https://osherove.com/blog/2004/6/4/managed-smart-documents-wrapper.html) - Jun 2, 2004 ### [Israeli .Net User group meeting today - you coming?](https://osherove.com/blog/2004/6/2/israeli-net-user-group-meeting-today-you-coming.html) --- ## About the author **Roy Osherove**: Senior Solutions Architect at AWS working on AI for production and AI-driven development; author of The Art of Unit Testing and Elastic Leadership, with about 20 years of consulting and training on unit testing, TDD, team leadership and continuous delivery. ### Sites - [RobotPaper](https://robotpaper.ai/): This blog: AI patterns and anti-patterns, AI and coding agents, and engineering leadership. - [osherove.com](https://osherove.com): Roy's personal site. Author of The Art of Unit Testing and Elastic Leadership; consulting and training on unit testing, TDD, team leadership and continuous delivery, plus about 20 years of blog posts. - [The Art of Unit Testing](https://www.artofunittesting.com): The Art of Unit Testing, 3rd Edition (Manning): readable, maintainable, trustworthy unit tests, plus TDD workshops in C#, JavaScript, Java and Kotlin. - [5whys.com](https://www.5whys.com): Roy's writing on software team leadership: self-organizing teams, surviving chaos, learning mode and the Elastic Leadership model. - [Pipeline Driven](https://pipelinedriven.org): Continuous delivery and DevOps practices: build patterns, pipeline-friendly testing, DevOps metrics and enterprise DevOps. - [Elastic Leadership](https://www.elasticleadership.com): Elastic Leadership, Roy's framework for software team leaders (survival, learning and self-organizing modes). ### Social - X: https://x.com/royosherove - LinkedIn: https://www.linkedin.com/in/osherove/ ### Contact - Contact form: https://forms.gle/jQSx5KoXvrVA1JCK7 ### License Licensed under CC BY 4.0 — reuse, quote and adapt with attribution (Roy Osherove, link to the original page). License: https://creativecommons.org/licenses/by/4.0/