DCSIMG
November 2008 - Posts - Product Readiness

November 2008 - Posts

ALM User Group - December Meeting

The December meeting of the Israeli ALM user group in Microsoft will deal with the facsanating subject of Agile Development and the steps that a software organization should implement to achive the transition.

 The group meets on the second Monday of each month (on December, second Monday is the 8th) in the Dekel hall in Microsoft offices in Ra'anana. Meetings start on 17:30.

The user group page: http://www.microsoft.com/israel/communities/usergroups/. unfortunetly you can't register to the events from the group page, please use http://msevents.microsoft.com/CUI/EventDetail.aspx?EventID=1032396580&Culture=he-IL

 Meeting's Agenda:

The Agile transition:  Pragmatics steps required for a successful transition to Agile methods

Agile developments and scrum are no longer new buzzwords in the industry; almost everybody must have heard about it or even attended a lecture or two. In this meeting of the ALM user group we would like to move forward and discuss the pragmatic steps required for turning the agile concepts into pragmatic activities. We will discuss the implications on the people in your team, your working methods and of course your tools, and  how team system can support you in the transition.

17:30 – 18:00 assembly

18:00- 19:00

 The Agile transition framework:  How to build a successful Agile transition process  (Eyal Katz – founder of DevManage).
In this session we will discuss the challenges and suggest solutions for a successful agile transition. The process is based on adjusting the framework to the specific needs for the people, methods and technology of your organization
.

19:00 – 19:15 break

19:15 – 20:00

Agile case study – my transition experience as a Scrum Master - Gal Possek, Program Manager and Scrum Master, Amdocs

 

 

Dev Academy - The Team System Panel

Microsoft Israel is holding the Developer Academy event for the 3rd time on December 15th. The target audience are developers and technology professionals and will include a variety of lectures and panels. I will participate in the Team System panel and would like all of you that have an interest in Team System or ALM to attend.

Panel description: 

PNL03 - Align the development process with the Business using Visual Studio Team System
The current situation forces us to cut unnecessary expenses and align our development process with the business. In this panel we shall discuss the following issues in order to help you better focus your efforts: Team system deployment – Do it your self, Agile vs. Scrum and CMMI best practice for selecting process template, Glimpse from VS2010 and new power tools and Team system for non .net development teams

The chasm between product delivery and sales

Many years ago there was a legend from a big well known technology provider called Digital (old boys should remember, young guys, well, check Wikipedia). The legend said that on sales “missions” the engineers would never have a glimps of the customer before the deal was done. This enabled the sales rep to sell his dreams, collect the order and… run away hoping never to see the customer again in the office or for that matter in a dark ally as well. When the deal was done and the project was started the engineers walked in, looked at the product that was sold, then looked at their own “creation” and felt sick to their stomachs. “Where is that ******* sales guy” they muttered – nowhere in sight.  Those days are long gone.

These days when we sales guys walk into our customer meetings, we are armed with an endless array of sales documentation detailing features and specs, demos, brochures and nearly every dreamed, paper worthy, description of the product we are selling. Obviously the selling leeway is much narrower thus creating a huge “trust” between sales teams and their product/R&D colleagues. The trust is in the real understanding “the product really does what it says on the cover”. Well experience shows that, over selling by sales reps is usually (not always) coupled with under delivery by the product teams, so we are selling today the n+4 version of the product which will be available in 18-24 months time… this is a recipe for disaster.

One of the biggest holes in knowledge amongst sales staff is what really is there under the hood of the product and how to sell its current benefits. Too many times we are lectured by R&D about features 16, 17 & 18 whilst only the product people really know that they have barely got past feature 9… and that a deliverable product at any stage is only available 6 month from now…
Let me share with you some real life examples, which I am sure are not unique:

The company’s executives are pushing the sales team to deliver POs (purchase orders) at short notices. “We have a great product, just what our target customer needs and we are 9 months ahead of our competition” say the headlines. So the sales crusaders set off to the sunset to sell, armed with the “knowledge” that all is in place.
So a few months of work and here we come back with an agreement with a large multi-national customer operating in multiple countries – big opportunity, the one we were all expecting. Easy, we say, all we need to do is to give a product to each country for testing and a few weeks later, come back in to sign up the customer… We (Sales) are counting our sales bonuses and the management is leaking info to the investors – “the big one is being reeled in”. What happens next is the tragedy of misalignment between sales and product people… “the Product is late”, they say and we should wait “just a few more weeks”. Anger builds but we are seasoned professionals, we can set expectations with the customers and get over this unforeseen delay. Then come more delays, and yet more. The end is quite obvious; from a great opportunity, a commercial disaster is born. The characteristics of the disaster are many but could be summed up simply through lack of transparency and coordination between sales, marketing and engineering which causes chasms in product and sales understandings. The same chasms that were illustrated for Digital at the beginning of this entry.

In the next few entries we will examine how such chasms should be bridged in order to create an effective selling organization which not surprisingly starts not in the sales team but rather in the R&D, engineering and product side of the house.

Stay posted, more to come.

Tal

On the road to sales and product alignment
I once worked in an oil and gas project where the IT component was less than 5% of the total cost. One of the senior managers from the oil company told me he wants to have a bet with me that the IT element will be late and cost more by at least 10%. His argument was that we in the IT business have all the best methodologies (usually copied from other industries) but we rarely deploy or stick to our own preaching.

It is quite common to hear arguments between sales people and product development (product people) regarding the true status of product availability. Sales people will always sell what they can and easy and promise the heavens. Product people will try to bring them back to reality or join in the enthusiasm and agree to deliver features and elements that do not exist. We all know the end result of such discussions – the client has delays and usually has to pay more.

All of this can be fixed in a very short time but it requires the human factor to be better managed. I am not a tech head! I am a marketer but, Application Life Cycle Management (ALM) and Product Life Cycle Management (PLM) are a set of methodologies, processes and tools that I promote as they help me to bring more value to the vendor and to the customer. Alignment and discipline are keys to a cost effective and measurable value all around.

Think about it this way - When a sales organisation works in partnership, enabled by transparency and common goals with the product group it has a better chance in selling a product. The customer has detailed understanding of the delivery and the true costs required. The holy grail of up-selling and cross selling becomes simplified as the trust between buyer and supplier exists. The value of customers is not only in their expenditure with you but also in how they promote you and add to your brand.

If this short description and scenario sounds familiar then next time I will be expanding on some of the first things to implement on the road to sales and product group alignment.

By the way, the manager from the oil company was right!

Real value of Application Lifecycle Management
There are so many definitions for application lifecycle management out there; almost all of them discussing the relations between the phases of software manufacturing. There were times that I completely agreed with them, and don't get me wrong,on the methodological level: I still do, but on the practical level I think they left out the most important part: lifecycle management is all about cutting costs and effectively using resources to optimize your product value. IIn my opinion, the key success criteria for lifecycle process implementation are whether the business is able, at one glace, to find out the complete expected expenditure on a new feature and the timeline for its release. Software development should not be looked at through a foggy glass; all the information should be available and crystal clear for the decision makers. Once we are technically able to measure every new requirement coming from a customer or a feature suggestion by our product manager by its real value: the amount we are about to spend building it opposed to the expected volume of sales and revenues, only then we gain the ability of achieving well balanced technical/business decisions and focus all our efforts on the features necessary for our product success.