My Reaction on the Book Getting Real… =) * chapter 7

In this chapter the author tries to tell us that in every organization there should always be unity. In all the things they do, work with and etc. there should always be unity. They should always have the check and balance. We should not let things get lost. We should hire people or talents with many talents so that they can be creative during the development process. With these talents the result of your application would be better.

A person sometimes needs to work alone, with these they are challenged and needs to creative so that they can achieve something. Working alone is hard but sometimes it’s helpful because you have no one for whom you can depend on. Some people work in the evening because they are not bothered and their brain functions more in the evening and vice versa. Whether they work in the morning or evening they all have this one goal that has to be achieved to finish their application. Interruption is your number one enemy because if you get interrupted you will be starting all over again. Working alone means that you don’t have communication at all. This means that you should have no messaging, e- mail, and etc. just go and work alone.

You don’t need to have meetings because it is just a waste of time. Instead of having a meeting why don’t you try simplifying it and work alone. You can have meetings in an email or messaging but you don’t need to meet. If you have to really meet with your colleague you should set up an agenda of the meeting, set up a 30 minute meeting and invite few people as possible to avoid long conversations.

Motivation in working is the most important thing to consider. Without it you don’t have the concentration, you’re not working hard lastly you will not think creatively. If you’re not motivated the chances of having a good project will be low. Long release of motivation kills you and your application because it keeps you waiting. This book tells us that make something that you can release or finish then that’s the time you can celebrate for having a successful project. With this builds morale, increases motivation, and reaffirms that the team is headed in the right direction.

ZEN GARDEN SITE

http://www.monica26.site90.com/

sori for the late post…

My Reaction on the Book Getting Real… =) * chapter 6

In this chapter it talks about how you would make your application better by thinking what would not work and would not help you in building the application. This would think would be prioritized first. Like the previous chapter of this book it prioritizes the things that must be done first. We should not go on to details because it will be a waste of time.

The book helps us think what should prioritize first and not to go on to details. This book also tells us that all of us make mistakes. Let’s not be a perfectionist because it will not be helpful for our application. I think no one gets something smoothly or did not go to a hard process. The book tells us to analyze the things or thought is missing in the application and if there are some problems it tells you to start the process all over again.

Work with iteration. You should work your application by process. You need to finish the first process before moving on to the next. You should first do the brainstorming because it can really help you to make the application faster. If there are some problems that will occur while doing your application try to solve it. Don’t feel that you have done wrong when you encounter problems but you must feel the excitement because with the problem that you have encountered you might learn something and you can have a better application. Having problems or mistakes is not a big deal. We will be encountering it often.

Don’t forget to finish the first process then proceed to the next until you finish the entire application.

My Reaction on the Book Getting Real… =) * chapter 5

In this chapter it tries to explain to us that if we build a project we need to build the half of it successfully by combining your ideas by taking whatever you think your product should be and cut it in half. Compiling your ideas and run through it and you’ll see that you have made a good one. We should Start off with a lean, smart app and let it gain traction. Then you can start to add to the solid foundation you’ve built.

Most people would ask these questions “why didn’t you do this or why didn’t you do that?” but the most favorable answer is because it just doesn’t matter. That statement represents a great product because some of the people would try to destroy you when you have a successful application.

The best designers and the best programmers aren’t the ones with the best skills, or the nimblest fingers, or the ones who can rock and roll with Photoshop or their environment of choice, they are the ones that can determine what just doesn’t matter. That’s where the real gains are made. In making an application a programmer doesn’t need it to be beautiful as long as the information that needs to fill in is there and a real programmer should know what is the thing that just doesn’t matter.

In adding some features it is a hard process because when a process of adding a feature failed you’ll be stuck. You should only consider features if they’re willing to stand on the porch for three days waiting to be let in. you should not always agree on what the customer wants but you can always listen to them but you don’t have to do it because it is a very hard process and it is also hard to implement. You must tell to your customers that their suggestion will not be implemented immediately. But if they keep on requesting the same thing maybe that’s the time to start to implement it

You should build a product and offer services that you can manage. Because when you can’t manage it, it will just give you problems. If your building an application, make sure that you can manage it, finish it, control it. Make sure whatever it is that you’re doing is something you can actually sustain — organizationally, strategically, and financially. Some of the customer can’t afford on the price you give them so before you start an application make sure that the price is affordable.

Should I go with a Vertical CRM or Best of Breed CRM?

So here I am plugging through the summer and things are busier than ever.  As I have mentioned in the past things go in cycles.  Recently, I have been involved in more and more meetings involving conversations relating to the pros and cons of vertical or industry specific CRM solutions and what I would call mainstream, or best of breed CRM technologies.  I wish there was a simple answer regarding which direction companies should go but there are some specific questions you should answer to help guide you through your specific situation.

Divergence – This is a subject that I talk about with clients as it relates to the core business and how much their sales and service activities and operations diverge from main stream CRM technologies.  If the nature of your business is so unique that there is a vertical solution that has captured the essence of that uniqueness then you might be better off with a vertical solution.  What I tend to find in many instances is that operations are not usually divergent enough to warrant a vertical solution.

Business Risk & Investment – When assessing the capital and investment of CRM companies you should look closely at the core business of a vertical CRM solution and whether or not there are competing factors for research and development dollars inside that company that will affect the ongoing improvements that you will need in your CRM solution. While a best of breed application may bring generic improvements many vertical solutions are slow to evolve because the CRM may only be a module of a broader solution.

Usability – One of the best measures of a vertical solution is to follow the workflow of the system while going through a demonstration.  If the solution is lock step with your business model then this may provide a short time to  value and an easier implementation.  Be cautious if the system does not provide key elements of your business because many vertical solutions are inflexible or hard to modify.

Flexibility – Over the years I have migrated many companies from vertical solutions because their business evolved and the company entered new markets or began to provide other horizontal solutions that could not be handled by the limited scope of the vertical CRM technology.  Like it or not many companies change over time for business survival and many best of breed systems can handle multiple business workflows for different lines of business.

Integration – So this one is tricky.  When vertical solutions are deployed many times the key data needed by personnel is housed in other solutions within the firm.  If this is the case the vertical solution should have an open platform capable of integrating other applications seamlessly.  Best of breed CRM platforms are usually designed with tools capable of robust integration because this is often a requirement of the firms that deploy them.

Depth – Another challenge with many vertical solutions versus main stream CRM applications is the depth of functionality. If the solution will handle your needs but is so deep in capability that you don’t need a great many of the capabilities then it might be a challenge to deploy and make the system easy to use.  If your user community is encumbered by complex workflow or driven to use multiple screens to achieve simple tasks then you might be in trouble.

Of course there are other key factors when deciding on a CRM solution for your organization like cost, licensing options and deployment options (SaaS, web, offline to name a few). But, take a smart approach to figure out a scorecard of what is most important now and what you might need in the coming years.  The answer on which type of solution will be a best fit can usually be achieved by asking and answering the right questions.

http://blog.practicalcrm.net/2008/08/28/should-i-go-with-a-vertical-crm-or-best-of-breed-crm.aspx

There are some specific questions you should answer to help guide you through your specific situation and these are Divergence, Business Risk & Investment, Usability, Flexibility, Integration, Depth. This can help your system in making it better and can have less problems about it. There are other key factors when deciding on a CRM solution for your organization like cost, licensing options and deployment options (SaaS, web, offline to name a few).  This are just few ideas on how we have a better and more effective system.

Retail Technology Experts (RTE) Announces Acquisition of Clever Computing,Inc.; Opens Branch Office in Minneapolis, MN

RETAIL TECHNOLOGY EXPERTSTM (RTE) today announced the acquisition of the Minneapolis, Minnesota based Retail Pro and Microsoft Dynamics RMS Partner Clever Computing, Inc.

Miami Lakes, FL September 2, 2008 — RETAIL TECHNOLOGY EXPERTS (RTE) today announced the acquisition of the Minneapolis, Minnesota based Retail Pro and Microsoft Dynamics RMS Partner Clever Computing, Inc.

Clever Computing, Inc. is a Retail Pro Master Platinum Business Partner and a Microsoft Dynamics RMS Certified Partner that has been providing retail software solutions to retailers in the Midwest since 1989. Currently, Clever Computing, Inc. supports over 200 clients, representing over 500 locations throughout the United States.

“With more than 30 employees, this new organization has many seasoned experts with very broad experience to support our clients. This is a very positive move for our clients, our staff and our business growth opportunities” said George Hipp, President of Clever Computing, Inc.

“We are looking forward to integrating the Minneapolis team into RTE. The combined expertise of the two teams will allow us to expand nationally and better service our customers. This acquisition also moves us closer to becoming a national player in the retail technology industry,” said Mahendran Ramanathan, President of RETAIL TECHNOLOGY EXPERTS (RTE).

RETAIL TECHNOLOGY EXPERTS (RTE) is an innovative retail technology solution provider that has been providing turn-key technology solutions to retailers for the past 17 years. RTE’s experience in retail and specifically in retail technology affords the retailer an expertise second-to-none in their industry. From initial discovery to implementation and on-going support, RTE offers retailers a true strategic partnership.

http://www.newsguide.us/technology/hardware-peripherals/Retail-Technology-Experts-RTE-Announces-Acquisition-of-Clever-Computing-Inc-Opens-Branch-Office-in-Minneapolis-MN/

Clever Computing, Inc. helps other companies in making their system well. They have employees that are seasoned experts that has many experiences that can help the customers in handling their systems. It is an advantage to the Clever Computing Inc. because they have different employees or experts every season with this the customers will be going back to them because they have different ideas in helping the system to be better. It is also an advantage that the two companies will be merged because they have different perspectives and ideas that can help the customer.

Vertical solutions based on TikiWiki – An opportunity for open source entrepreneurs and consultants

The June 2008 report on “Collaboration and Social Media” by the Gilbane Group suggested that “the future of social media focuses on delivering vertical solutions complete with rich domain expertise.” This is a view that I have found to repeatedly ring true.

This further reinforces my belief that open source collaboration solutions are inherently superior to non-open source alternatives because open source allows for the widespread proliferation of different vertical solutions based on the same platform, by different members of an extended community. Open source provides the framework within which each vertical solution provider can maximize their chances of success by being extremely focused, at the same time benefiting from economies of scale and scope by being part of a larger community.

In open source environments, value is primarily created (and monetized) by “maintainers” of the code who keep each vertical solution up-to-date and relevant to the needs of targeted users, since the “stock value” of the code has been communalized. The cost of maintaining the code is shared, enabling each vertical solution provider to incur far less cost than if they were to develop the solution using a proprietary model. At the same time, their competitive differentiators are not undermined, since code does not stand still – it requires constant maintenance and “flow values” generated by the “maintainers” is what customers will pay for.

As there are countless vertical solutions possible with a platform as comprehensive as TikiWiki, this presents a remarkable opportunity for entrepreneurs and consultants to take on responsibility for maintaining new vertical solutions for markets that they have relationships in, and to monetize it in the way most suitable for each market.

We hope more and more open source entrepreneurs and consultants will join in. There are significant developments at the core of the TikiWiki community to facilitate this, for example, the upcoming Installation Profiles system and TikiWiki “Magic” (codename for the new data driven admin panel) will make it much easier to configure and maintain different vertical solutions.

http://nelsonko.com/2008/09/14/vertical-solutions-based-on-tikiwiki-an-opportunity-for-open-source-entrepreneurs-and-consultants/

I think that tikiwiki helped a lot in facilitating the open source entrepreneurs and consultants. There is an advantage having a vertical solutions because it helps these open source entrepreneurs and consultants by being more focused and updated.

My Reaction on the Book Getting Real… =) * chapter 4

Well in this chapter we will be tackling about building an application. Why did we build it? What is the purpose of building that application? What does this application stands for? We should know the vision of your application. This vision can guide you in improving and in decision making. We should think big with regards to our application. Our vision should be brief because when we have a vision that is a paragraph long we could be having a hard time in remembering our vision. Visions must be flexible because time passes and the technology is improving. “Instead of limiting communication to within a firm, we gave clients access too” this means that we should be open for the employees and customers suggestions because sometimes they have great ideas to improve your application. “Make the big decision about your vision upfront and all your future little decisions become much easier”

“Success and satisfaction are in the details”. This statement tells us that we find our success and satisfaction in details but we can’t just find them in details we should also consider some of the things like stagnation, disagreement, meetings, and delays. This can be a threat to you and this can cause lower chances of your success. You should not stick yourself in just one detail but you should focus on the whole process because it can cause delays and disagreements. You should not first focus on your font, design and etc but you should finish it first so that you will not cram.

Sometimes we are already thinking of the future problems that we haven’t encountered yet but we should not focus on them because we can’t finish our application. When you already encountered it that’s the time you think of solutions to your problem. You don’t need to build a perfect application because there is no perfect application you will be encountering it as time goes by. You will slowly increase hardware and system software. You don’t need to over stress in solving your problem but explain to the customer what is really happening and for sure they will understand.

The customer is not always right. We should have to sort out what’s right and wrong for your application. You don’t need to please anyone but we have to be patient enough to find for the right customer.

You don’t have to create a perfect an application but create a great one. You may encounter some problems as you go along. And this problem you should solve in one at a time. No one can solve a problem in a bulk. But in creating a great application your application should be flexible enough so that if there should be some changes or upgrades you will not be having a hard time in fixing it.

My Reaction on the Book Getting Real… =) * chapter 3

In the third chapter of the Getting Real book the first topic is about “Less Mass” and it it’s said that “The leaner you are, the easier it is to change” because now a day the there are more new gadgets coming out and in the system that where going to produce we need to be flexible so that when there are changes we can easily adapt it. The second topic is about “Lower Your Cost of Change”. In this topic it is said that “Stay flexible by reducing obstacles to change” because we need to be very flexible if there are changes made. The best way to change is not about the cost you’re going to pay or invest. Change should be easy and cheap. Because in our generation we should be wise in order to be successful. We can change by not really losing much of your capital. The third topic is all about “The Three Musketeers” it is said in this topic that “Use a team of three for version 1.0” because we should start with a small group and with these small group we can be a successful one. By starting a small it is hard but when you the right colleague you will not be having a hard time in creating an application or a system. The lack of man power is the most challenging part of starting with a small group with these you can be more resourceful, more patient in dealing with your colleague and many more. The Metcalfe’s Law and project teams states that keep the team as small as possible. The communication flows easier in the small teams rather than a large team. The next topic of the book would be the “Embrace Constraints” with this topic it is said that “Let limitations guide you to creative solutions” because there is no much time, money and people in doing the project so you need to know your limitations so that you will not cram when the deadline is near. The last but not the least topic is “Be yourself” and it is said that “Differentiate yourself from bigger companies by being personal and friendly” because a lot of small companies makes mistakes by pretending to be a big ones so you need to be yourself by knowing the advantages of having a small group. I have learned in this chapter that the smaller the team is the better the outcome of the project, lesser cost, and in a smaller team you will not be having a hard time in communicating with your colleague.

My Reaction on the Book Getting Real… =) * chapters 1 and 2

When I finished reading the book I have found out that Getting Real is about making your life easier but making it in right way, achieving your goals in a shortest path or ways, and you need to be happy in what you’re doing so that you can tell that you have achieve your goals. Lastly, how you are going to compete with your customer in a different aspect. For example, you will be thinking on how you will be able to win over your competitor. You will also think that you will win over your competitor by not being a cheater but you have to be creative on how you will improve your product.

You should also know your competitor by knowing the process of making their products, their strengths and weaknesses. It is also mentioned in the book that when your competitor makes the products faster the best way you can beat them is to lower the price of the product.

But before you know your competitor you should also know your product, strengths and weaknesses, and what are the problems of your product. You should enjoy on what you’re doing so that when you have achieve your goals and saw your customer were very satisfied with your product you would still continue on what you’re doing because you are enjoying it at the same time you fulfill the needs of your customer