Wednesday, October 9, 2013

Open Source: 
Is it always free.
The common terminology of open source refers to software that is offered for free for public personal or business use.

Who contributes

The creation of these products are usually a wide collaboration of people that work together in their personal time. Large projects may require the work of hundreds of people and they may receive small donations of users of the product. The open source projects can be found online and are always in need of help

Products offered and why Pay?
The most common software that is available are Unix and Linux distributions. According to market research it has a little bit under a 5% market share. With its competitors as the giant Microsoft and the fancy Apple. They also provide server distribution and they recieve a lot more attention than personal OS. With Linux distributions such as Red Hat theres is a long list of software for them. Such as Gimp which is a photoshop and Open Office for normal writing uses. The list is endless
Source: MarketResearch


Source: MarketResearch


So with all of these options what keeps up from using the alternatives.

Almost everything now a day can be found for free either online or from an extra cd that your neighbor has bought. Yes there are various copyright laws and many infringements, but I do not know one person who does not download music. So the question is how far are you willing to take it. There are endless torrent websites that contain Adobe Master Suite to movies in theaters and etc. If you want something you will be able to find for free. While it is true that paying for a product allows you to redeem services, technical help and warranty which is necessary for companies. For personal use I pay for a very minimum of the software I use whether it is under a free trial license or just open source software such as notepad++. 

Sunday, October 6, 2013

Agile: Moving forward

AGILE:


     What is Agile Development and what can it do for your team? 
   
In the past companies have conducted projects by using a Waterfall approach which would be considered starting from the beginning and moving step by step and advancing further. The problem with this though is that it does not allow as much room for change. Changing a phase one would mean redoing every other step after it that relies on the foundation. Apprehensively it is a very linear approach.

Look below and lets say a group approaches the same project with the same ideas and requirements in mind. But in order to achieve the final result they can take a different route. On the right side it shows the Agile chart, you can see how things are done almost at the same time and are iteratively processed. In the 2nd step the Initiation and Analysis are done at the same time and can be redone and change without delaying the timing of the project. 
The team that endorses and are the main founders of the Agile method has a Manifesto for Agile Software Development on their webpage. In it they describe in a short simple paragraph the idea and use of their method.

In the Work Place

Microsoft endorses the use of Agile for software development as stated in their Research Page. They prefer the variant that uses Scrum. They like the implementations on small scale projects but have doubts and concern on large projects with 20 members or more because the design is not as sustainable with such a large amount of people.

Overall when deciding which method to use whether Waterfall or Agile or any other development Model. Timelines, experience, resources, and requirements should be the factors in deciding your plan of action. With a Waterfall method, things can be executed faster and quicker so simple and small projects with definite requirements can be completed. With more freedom on a project I would prefer the Agile method because there would be more room for improvements or mistakes