![]() In hind sight, it's a no-brainer (though it was far less obvious back then). instead of starting with a big mess and integrating changes from a solid code base, start with a solid code base and only merge rock-solid features into it. I think the scheme they came up with made great sense. When folks finally came up for air and looked at Longhorn, the reset made sense because the Server 2003 code base was rock solid whereas some devs had been mucking with Longhorn unchecked for years. Very little actual quality assurance was going on because those folks were just too busy shipping other good stuff. The ones that were, were distracted with a new test harness and in learning/writing managed code automated tests. The testers weren't really even looking at it. Release management had their 3rd string assigned to Longhorn. During this "distraction", it was primarily devs that were working on Longhorn, and they were doing so in different branches. One comment makes a really good point about why the Longhorn reset was a good idea:įWIW, the Longhorn reset was due to the fact that the main folks were distracted with Windows Server 2003 SP1 and then Windows XP SP2. The copy I have has the title Day in the Life of a Developer. Perlow, moved on to Google last year or so. I think I know - search the internal web for the PowerPoint named something like "BillG A Day in the life of a Dev" or such. Who was it that tried to fix the mess but went to Google instead? Other random things: one comment following up on my last post: Sorry, it's just me, my beat-up laptop, and a bunch of groovy people taking time to add their points-of-views. I don't know whether to be flattered or insulted. Hmm, I am starting to think this is just a PR stunt, this blog is fake.įollowed up into more depth here. This blog is a place where people will blow-off steam and, having satiated their anger, be a compliant cog and jump back into the machine. They even got an amazingly good looking flunky, posing as the blog's author, to meet with a respected Business Week journalist. This blog is in fact organized by Microsoft leadership to make upcoming major changes and shake-ups appear to be organic and therefore easily accepted by the subtly manipulated rank-and-file workers of the company. Where are the Lone Gunmen when you really need them? There is no Mini. Worth a quick scan ( as always, interesting documents noted in ). The Annual Meeting of Shareholders of Microsoft Corporation will be held at theĮxecutive Pay: now, within the Microsoft DEF 14A filling is information regarding pay and bonus for some of our executives. perhaps have your concerns heard between bursts of sunshine and smoke. November 9th - Save the Date! Have you ever been to the shareholder's meeting for Microsoft? Well, if you're a shareholder and you want to experience the meeting. Published stack ranks would be demoralizing? Is peer-review more screwed up and political than stack ranking? Can you incorporate a 360 assessment for everyone? Can manager feedback be constant and actually affect the manager's review? How about if you could provide feedback all the way up the chain? Should everything be transparent: if you're going to keep a stack rank, should you just publish it? If not, why? Managers feel like they can actually tell people when they do a good job ( versus having to hold their tongue should that report be on the edge of falling into the 3.0 bucket and then being confused when that 3.0 review is delivered). They feel appreciated, well compensated, and can focus on doing a great job. People have written me saying how great it is to be with companies that reward all-around performance vs. Now, I imagine there's something worse than stack ranking. ![]() What I would deeply appreciate is real-world experience from people living with stack ranking alternatives. In some ways, we're slipping backwards into the industrial-era muck. I'm also taking some time to contemplate on Deming's points and assess how Microsoft is doing against them. focusing on how to politically get ahead to get a good review. ![]() Alternatives to " Rank and Yank" stack ranking: rather than playing around with Monad or writing some gadgets, I've dedicated my free time to reading up on what to do after you get rid of stack ranking and try to center on having everyone actually work together to get the best results for the customers vs.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |