Skip to main content

Open workbench an MS Project Open Source Alternative

For a project manager , planning is your bread and butter . A good software tool is a complement ,as long as it doesn't come with a high price . MS Project , a Microsft product , is one of the most commonly used project management tool around . But if your just a low earning firm with little money to invest on project management tool you may not be able to afford this tool.

Open source software , as I always mention it on some of my blogs , free users of high prices from large software companies . It may not be always free , but it is cheaper . Additionally , the source code comes with it , so if you are that technically adventurous , you can always customize it to fit your need. Open Workbench aims to be a direct alternative to Microsoft Project . Open Workbench provides project planning and scheduling together with resource management. Open Workbench even offers import of Microsoft Project files - to make migration easier . So if you dont mind investing a little of your time to learn the software , in the long run , you may appreciate how much is being saved on using this software. Personally , I have tried using the software (my project management task was short lived so i was really able to jump into it deeper) and all I can say is that , the software can be easily learned to achieve the productivity you want.



Visit their website , it has a lot of information regarding the software plus they have a SAVING section on the page that shows how much can you save. Dont forget to download it and give it a test drive.

Comments

Anonymous said…
It's a good blog, smile for you 1

Popular posts from this blog

Getting Started with Stateless : A Lightweight Workflow Library Alternative for .NET

Image Credit: https://www.pioneerrx.com A year ago, I was looking for a simple workflow manager for a project I was working. Its a medium sized application that involves tracking the state of assets in the system. Back in 2008, Microsoft (MS) introduced new technologies along with the release of Visual Studio 2008: Windows Presentation Foundation (WPF), Windows Communication Foundation (WCF), and  Windows Workflow Foundation (WF). Having worked in a company utilizing mostly MS products for development, my first option was to go with WF. After doing some time reading and studying the library, I paused and decided it was too complex for my requirement. Using WF would be an overkill and the fact that it has, a rather, steep learning curve, there has to be another option. My mind toyed with the idea of developing a simple workflow library myself. It would be a learning experience but it might end up consuming a lot of time. Why reinvent the wheel? So I started querying the ...

Hiding Unwanted Python Folders and Files in Visual Studio Code

Visual Studio Code is a universal editor and pretty good at it. However, the explorer view maybe cluttered with the automatically generated folders and files confusing developers. Python is no different. Below are example files and folders generated by Python. The __pycache__ folder and *.pyc files  are totally unnecessary to the developer. To hide these files from the explorer view, we need to edit the settings.json for VSCode. Add the folder and the files as shown below: Copy and paste the lines below : "**/*.pyc" : { "when" : "$(basename).py" }, "**/__pycache__" : true

The Story Behind the Name C#

I remember one time in an exam for employment , the first question was - who is the father of C#? I have been working with the language but never did I ask myself who actually started the language ( of course Mirosoft was the brainchild , right? ) . After a googling expedition I found out who was the culprit - Microsofts Anders Hejlsberg . I was not interested why it was called C# then , but opening my VS2008 today , I stumbled on one of the articles being shown at the VS2008 opening page - "Computer World: The A-Z of Programming : C#". Its an interview with Anders discussing the history and beyond of C# . Heres the cool part , the name for C# prior to its release was actually COOL (C like Object Oriented Language) . Below are some lines taken from the interview: Why was the language originally named Cool, and what promoted the change to C#? The code name was Cool, which stood for ‘C like Object Oriented Language’. We kind of liked that name: all of our files were called .coo...