Welcome,Guest

What we are saying!!

Apurva

Apurva

Apurva has not set their biography yet

There are many Online Project Management products available in the market. All these tools provide different set of features and target various industries.


These tools range from simple task management and list management features like those provided by Trello, which can be applied across a broad range of industries but have limited features. On the other hand, there are products like Pivotal Tracker which provide project management features focused on Agile software development following a rigid process.


FindNerd provides a project management platform which bridges the gap by providing a rich set of features while still allowing the end-user to have the flexibility of using them as per their need.

Below is a comparison of the main features of FindNerd, Trello and Pivotal Tracker:

ÂÂ

FindNerd

Trello

Pivotal Tracker

Project Management

ÂÂÂÂ
Â

Traditional Project Management

Â

Agile Project Management

Â

Â

Users Stories

Â

Product Backlog and User stories prioritization

ÂÂ

Â

Issue Tracking

Â

Task Management

ÂÂÂÂ
Â

Scheduling

Â

Time Tracking

ÂÂ
Â

Resource Assignment

Â

Task Alerts

Â

Group Tasks – Milestones, Sprint

Â

Task History

Budgeting and Expenses

ÂÂÂÂ
Â

Forecast Budgets

ÂÂ
Â

Manage Expenses

ÂÂ
Â

Set Hourly Rates

ÂÂ
Â

Track Project Hours

ÂÂ
Â

Track Staff Hours

ÂÂ
Â

Invoice and payment tracking

Â

Collaboration

ÂÂÂÂ
Â

Document Management

Â

Forums

Â

Online Messages

Â

Chat

ÂÂ

Activity updates

Email notifications

Â

Online Meeting Tool

ÂÂ

Resource Management

ÂÂÂ

Â

Manage Resources & their Skills

ÂÂ
Â

Search Resource by skills

ÂÂ
Â

Resource Planning

ÂÂ

Â

Last modified on
Hits: 8117
0
As part of our software development services, we are involved in maintenance and enhancement for software products for our clients. At times, these clients want to explore the option of rewriting the application on some latest technology. Quite often the technical team is also keen on rewriting the application on the latest technology, rather than digging into the existing code base for providing bug fixes or adding new features. While it may be appear to be an attractive option for the development team to sell the idea of development from scratch on the latest technology, there are a few misconceptions and high risks normally associated with the 'rewrite to fix everything' approach:

- Rewriting the code will take less time than fixing the issues: Software development projects nearly always take more time than initially planned. The bigger the project, higher are the chances for it to have cost and time overruns. You may well end up adding many new bugs into the system and having to incur cost of many test and bug fixing cycles before having a product which can be released.

- Existing code base is messy: As the software tends to evolve over time, the existing code base is likely to be messy, and is likely to appear messier to a developer who has not been involved in the initial development. Even with a rewrite, it is very likely that the new code will end up being as messy as your current code by the time development is completed.

- New Architecture and Framework will address all the current issues: It is not easy to define an architectural framework, which can handle all changes and enhancements, which may come in the future and still withstand the test of time in terms of maintainability, scalability and performance. What are the chances, that the same or new mistakes will not be made in the new approach and you do not end up facing the same or some more serious problems?

- Cutting Edge Technology: You may start the rewrite on a technology  which is seen on the day as cutting edge, but by the time you complete the development it may not longer be seen as the in thing. Also your current code base is very likely on a well established technology with a wide support base, which is not likely to be the case with the so called cool and latest technology.

Some other high risks associated with the rewrite approach are:

- High Risk of failure - There is a high risk after starting the rewrite you run into serious issues which lead to abandoning the project. This is more harmful in the scenario when your existing product with a customer base has been neglected over this time period as you have moved resources for the new development.

- Missing existing features and workflows - While rewriting the code there is a high risk that you will miss some features and workflows of the existing product. You can be sure it is this feature your customer base will miss the most after release.

The most important reason for your product to exist and have a wide customer base is because it solves a customer problem and makes their life easier. This should always be kept in mind while defining the development roadmap for your product. Any decisions of change in technology or platform should be made with this goal in mind. 

The best approach for any technology migration for your product should be planned in a gradual and iterative manner. Some key points which should be part of your strategy are:

- Re-factor the existing code base. Take up parts of the existing code base to re-factor, add useful comments, test and release.
  The key word here is Re-factor.  This is the least risky option.
- Identify modules or components which can to rewritten and migrated to a new technology with the least effort and risk. This will give you insight on the technology and also validate your approach.
- Develop the core parts of your product on the new technology as a parallel development without affecting the support and evolution for the existing product.
- Your customers may want some new features on your existing product. It is a good idea to release this on the existing product and get valuable customer feedback rather than promising the customer and keep them waiting for the release of the new version.
- Be aware of the end-of-life announcements regarding the technology you are currently using. Plan the migration to a new technology based on this timeline so that you are not rushed into it.

If you take up the porting of your product to a new technology with the above approach and take steps to mitigate the risks, while ensuring that the support to the existing customer and their needs are not compromised, you are more likely to succeed.

Last modified on
Hits: 5325
0

Posted by on in Uncategorized

Recruitment Process Outsourcing ExplainedNumber of companies globally are increasing to outsource their work. The leading countries to which work is being outsourced is India, followed by China, Malaysia and Thailand. These are currently the top nations for outsourcing work, whereas, nations like Brazil, Indonesia, Bulgaria and Philippines are also coming up strong in this sector.

 

A few different sectors in outsourcing are BPO's, KPO's, Data entry, IT sector, Health sector outsourcing and Financial sector outsourcing. 

 

What we really want to talk about here is, Outsourcing with Consulting and Implementation. This refers to outsourcing of work by a company, by consulting it with an outside party. This brings in the importance of an Recruitment Process Outsourcing (RPO). When a third party takes the responsibility to recruit or hire resources for a business it is known as RPO. 

 

A third party can be vested with all the hiring responsibilities for a business or only some of it. While outsourcing, the third party becomes directly responsible for the outcome of the recruitments done by them. The advantages for a business or a company while outsourcing with consulting is that, they are relieved from the headaches in identifying the right resources and can also be assured that they are hiring professionals for recruiting the right people for them. 

 

These consultants or hiring experts, act as a human resource department for a company and once, a business module along with the set of responsibilities at each level is discussed with them, they can get the recruitment underway accordingly. 

 

Companies can choose to outsource both their entire work or partially by consulting these third parties. Outsourcing is primarily done by companies in order to check on the operational cost of their business. 

 

This is also the core requirement of small and medium enterprises, which exist in countries with really high corporate taxes and extremely high labor costs as compared to developing nations like India, where, besides the cost of labor being far cheaper than their own nation, it also has economic stability.

 

But outsourcing cannot always be a great and reliable option because by doing so a company shifts it responsibilities to an outsourcer. 

 

By doing so, they can never be able to keep a close check on the day to day functioning of their own business and have to count on the outsourcer for the same. From employing resources to identifying and directly assigning responsibilities, all lies in the hand of the outsourcer. Hence, it is consistently poses some risks in regards to the achievement of the desired result of that business. 

 

So it is always a great idea, to have a third party adviser involved, which a company can entrust with doing the outsourcing on their behalf and thus, eliminating the level of risk substantially and creating a sense of security.

Last modified on
Hits: 14002
0

Posted by on in Uncategorized

This is a true conversation I had with a client, followed by my email to him a few months after this conversation.

 

Client: I would like to have a high quality, bug free application for my customers.

 

Me: Our developers are excellent, but we would need a good testing strategy to make sure that the application that goes live lives up to your and industry’s quality standards. 

 

Client: We are a startup and would like to keep the costs under control and would like to keep the testing budget down. 

 

Client: You need to take care of the quality at the development level.

 

Client: We will also do the testing of the application on our own.

 

Me: Okay, that would be great.

 

I wish, I hadn’t agreed…

 

Dear Client,

It has been a pleasure working with you from the very start when you came to us with your idea. Brainstorming with you about converting your idea to a feasible concept to develop and bring it to market has been wonderful. We have been awed by the groundwork that you have done about your idea and the concept documents that you came up with. Over the last couple of months, we have crossed a few phases together where we have produced the visual designs of the application, finalized a solution approach, setup the framework of the application and have developed a few modules of your requirements. The journey so far has been nothing short of a roller coaster ride. 

 

But now we are on the brink of a situation that can lead to a big RISK. My fault was that I submitted to your suggestion about cutting on testing budget during our initial discussion. That decision has led to the following concerns. 

 

  • We do not have a defined testing strategy. We do not have a test plan or test cases. 
  • In the absence of test cases, our developers do not have a documented way of covering all cases for a feature. Do you know that QA is the best person to document your requirement at a granular level? They do so by defining all the positive, negative, corner cases arising from the requirements, thus providing the developers a wholesome view of what all criteria each functional module should pass. So, essentially QAs act as a Business Analyst and are the guardians of your requirements.
  • Our developers are not only developing the application, but spending considerable time in testing the application as well.
  • Not only is the developer, our project manager is also spending good amount of time in testing the product before it is released to you. 
  • And finally, you, our customer are also spending valuable time on testing. In a nutshell all the people are spending time on doing the work that neither they are supposed to be doing, nor they are experts in doing that. 
  • As a result, frustration is creeping in the team at all levels and despite going out of the box in doing that, results are not great. 
  • And the lowest of low, we end up spending a lot more that what we should have in doing this job. The reasons for this are simple.
    • The product has to be tested. Period.
    • If QA will not test it, other people like developers, PM and you have to test it.
    • They will not do a better job than trained and experienced QA, as they are not experts. 
    • They will not be able to provide that kind of coverage as professional QAs can provide. 
    • And, believe it or not, developers, PM and your time is costlier than that of QA, at least in our company and in general in the industry as well. 
    • So, we are doing what has to be done anyway, non-experts are doing it, spending more than what we should and we are not getting the best results. 
    • So, it’s a Lose-Lose situation for all of us and all of us are getting frustrated.


Before all of us go nuts working the way we are and go over budget, I request you to please look into the matter. We need a testing strategy and your project needs a test plan. I am here to help you devise one. I just request you to please see through the situation and realize that we are not saving money but losing it by ignoring QA. QA is essential part of a development project and Test plan is as important as a Development plan.

 

Your’s truly, 

Service Provider

Last modified on
Hits: 5475
0

 

Most Technology Start-ups take the following conventional approach in their endeavour to start a successful business :

 

- prepare an elaborate business plan

- pitch it to investors

- build a team

- develop and introduce a product

- sell the product

 

Research shows that 3 out of 4 start-ups end up failing in their endeavour somewhere along this path. In most cases, further the stage of the failure from the point of inception, higher is the cost of failure. 

 

The alternative Lean approach for Product Development by Start-ups is essentially based on the following philosophy :

 

- build a 'minimum viable product' based on continuous 'customer development'

 

In the Lean Start-up model the founders do not begin with a business plan, instead they begin with the search for a business model. In this approach, multiple quick iterations of experimentation and feedback are conducted which result in a business model that is executable.

 

This will typically follow the following sequence :

- Translate idea into business model hypothesis.

- interact with one or more customers to test the hypothesis and validate the assumptions about the customer needs.

- create a 'minimum viable product' to fulfill a customer need

- let your customers try out the product and get feedback

- based on the customer feedback develop the next iteration of the 'minimum viable product'

 

 

Business Model Hypothesis :

Founders are expected to briefly describe the hypothesis in a framework called Business Model Canvas. This involves listing out how the company will create value for itself and for its customers in the Business Model Canvas (shown below) provided by Business Model Generation. This is a template in which you need to answer a set of questions under 9 key areas resulting in the business model hypothesis.

 

canvas1.gif

Business Model Canvas

(SOURCE:WWW.BUSINESSMODELGENERATION.COM/CANVAS)

 

 

Customer Development :

Lean Start-up approach requires the founders to test their hypothesis with the potential customers. The founders reach out to the potential users, purchasers, and partners for feedback on all aspects of the business model including product features, pricing, affordable customer acquisition strategies and distribution channels. The feedback can result in the business model hypothesis being improved upon or an coming up with a new business model hypothesis by dumping the existing idea.

 

Agile Product development :

Lean start-ups practice something called Agile Development for product development. Agile development works hand-in-hand with customer development.

 

This approach does not involve the typical long product development cycles which run for several months and is based on assumptions of knowledge of customers’ problems and product needs. Agile product development aims to develop the 'minimum viable product' which include the minimum features for solving the specific customer problem. This minimum viable product is then tested with the potential users and customers to confirm that the objectives are achieved. This approach eliminates wasted time and resources by developing the product iteratively and incrementally and testing the 'minimum viable product' at the end of each iteration.

 

b2ap3_thumbnail_Agile-Development-Diagram.jpg

Agile Development

 

 

In conclusion, the Lean Start-up approach has the emphasis on nimbleness and speed and aims at reducing the cost of failure by the inbuilt mechanism of feedback and course correction at each stage.

 

New ventures can follow this approach to rapidly assemble minimum viable products and elicit customer feedback. This customers input is continuously used to revise their assumptions and then go through another development cycle, testing redesigned offerings and making further small adjustments (iterations) or more substantive ones (pivots) in case of ideas that are not working.

 

We at Evon Technologies have gained extensive experience in the above approach over the past eight years by working with many Start-ups. We can be a partner and service provider for Start-ups in their execution of the Lean Start-Up Model, by providing services in the following areas :

 

- Market Research

- Optimizing your Business Model

- Developing Market Requirements into Product Road-map

- Software Product Development and Quality Assurance

- Internet Marketing.

 

Learn More about Lean Startup Methodology : http://theleanstartup.com/#principles

 

Last modified on
Hits: 31152
0
Product Engineering, software engineering company, Product Development, Product Migration, Product Re-engineering, Product Maintenance, Product Testing Commercial Application Development, Business Software development, commercial software for startups, Application Support and Maintenance, software testing Product Maintenance, Outsource product maintenance, product support and maintenance Product Migration, Product Re-engineering, product re-engineering services Product Research, Product Engineering, UI Prototyping Services Software Testing Services, Quality Assurance services, professional software testers, Load Testing, Functional Testing, Cross Platform, Browser Testing, Test Automation, Testing Tools, software quality analysis Functional Testing Services, software quality analysis, Software Testing Services, Application Testing Services, Functional Testing Types Automated Testing, Automated Testing Services, automation testing, test script development, Automation Test Tools, outsource automation testing Load Testing, Performance Testing Services, Load Testing Tools Offshore Software Development, Outsource software services, offshore outsourcing services, offshore software development services, IT outsourcing services, software quality assurance services, Offshore IT services, Custom Application Development Services, Offshore Product Engineering Benefits of IT Outsourcing, Offshore Software Development companies, offshore software development firms Outsource planning, IT outsourcing, IT development services, offshore IT companies, offshore software development Offshore Software Development, Outsource software services, offshore outsourcing services, offshore software development services, IT outsourcing services, software quality assurance services, Offshore IT services, Custom Application Development Services, Offshore Product Engineering Offshore Software Development, Outsource software services, offshore outsourcing services, offshore software development services, IT outsourcing services, software quality assurance services, Offshore IT services, Custom Application Development Services, Offshore Product Engineering