The software development effort estimation is an essential activity before any software project initiation. In this article, I will illustrate how to easily estimate the software effort using known estimation techniques which are Function Points Analysis (FPA) and Constructive Cost Model (COCOMO).
The Consultative Selling: The Hanan Formula for High-Margin Sales at High Levels, 7th Edition by Mack Hanan is mainly targeting sales representatives to provide a specific and consistently successful approach and techniques for better sales.
I read the book and I found that it very helpful and useful for sales representatives.
Personally, I have met a lot of salespeople who are selling without knowing anything about the customer needs, challenges or strategies and they are selling products features without presenting the true added value of these products. I think you may have faced the same, especially with the infrastructure and equipment vendors.
The book offers some useful techniques and tips to enhance the selling process and make it value driven process to both customer and the seller. I think most of the big companies are using similar approaches and techniques mentioned in the book with different flavors.
I tried to summarize the key points which I think they are important to others while I do recommend to read this book. Here are the key lessons I learned from this book
The IT systems and applications are everywhere now, from simple to complex systems to run basic data entry to control autonomous cars and autonomous planes and more complicated systems.
Unfortunately, after a lot of research in software process models and project management frameworks, Software and IT projects still have a very high failure rate. According to a study has been made by Mckinsey at 2012
On average, large IT projects run 45% over budget and 7% over time while delivering 56% less value than predicted. That’s beside the common issues of deliverable quality of final software product according to specifications.
Another study from Mckinsey at 2014 regarding how to achieve success in large, complex IT projects.
The Enterprise Architecture concept has been introduced since 1960 by Zachman. Although it is still not widely introduced for many organizations, It becomes an important topic in Information Technology community and many organizations are trying to understand how it is important to have Enterprise Architecture capability within the organization.
In this article, I will try to illustrate what is Enterprise Architecture, why it is important, and what are the existing practices for that? And how you can start?
In our daily tasks, personal or work related, we usually face a situation that we have a variety of alternatives and there is a need for a decision process to pick one of them and to decide what will be the best to choose with a certain level of confidence.
These decisions can range from changing your job, selecting a candidate for a job vacancy, choosing the right software development life cycle, buy vs build decision or others. The common between all of them that they are decisions and they need a decision process.
In this article, we will discuss the process of trade-off analysis, and an example of different alternatives we need to select one of them. Read more
Everyone uses different set tools every day at his/her workplace to finish tasks faster, organize the work, and collaborate with others. Each moment new apps and tools are created and it is becoming harder for us to select the which one to use and which one offers the basic required functionalities which enable anyone to interact and use it easily and retrieve our data at any time.
I would like to share with you a list of tools which I’m using mostly every day in my workplace and personally to organize things, explore new ideas, or even brainstorming. The good about these tools that they are free, portable, and compatible with all kind of devices. I hope you will find them useful.
The system should be easy to use.
The system should be flexible and scalable.
The system should be secured.
The system should be portable.
Did you read any requirements document and found one of the requirements statement mentioned above? Then, you started to think, what does it mean to make the software ease of use, how can I make that feasible, if I implemented that feature would the software became more usable? would it be acceptable from the customer? What are the metrics and acceptance criteria for that? How to transform these intangible requirements to something tangible can be implemented and measured.