If generating SQL queries, data analysis, and conducting requirements JAD sessions is your fotrethen we need to talk.
You could join us for a 12 month contract which offers occasional travel to our client site in the US.
There are plenty of roles to go around as we are looking to fill 3 positions.
category
published
March 27, 2012
Systems Analyst
category
published
March 27, 2012
Sr. Systems Analyst
If generating SQL queries, data analysis, and conducting requirements JAD sessions is your fotrethen we need to talk.
You could join us for a 12 month contract which offers occasional travel to our client site in the US.
category
published
March 15, 2012
New Grad – Technical Developer
If you are ready to start your career in a fast paced and dynamic environment than we want to hear from you. We train and develop our Technical Developers to be capable of doing analysis, development, design, and testing. Yes, you will be stretched if you work here.
category
published
March 1, 2012
3x Intermediate Java/J2EE Developers
We are looking for 3 strong intermediate developers to join our newest project which kicks off in early March. Contact us if you fit the bill.
category
published
December 1, 2011
“Social” Status Reporting
Whenever we procure services from a vendor (e.g. remodeling a kitchen), we are faced with overcoming the fear of potentially spending a lot of money without getting a successful result at the end. Once the project begins, our visibility into project progress is then limited to what we learn from the vendor’s status reports, and what we see as visible progress. Unfortunately, we never really know if the vendor is painting a rosier picture than reality might reflect. Also, it’s often the case that visible progress is not easy to come by, especially in software projects where the work product is so abstract.
So our visibility goes down, our stress levels increase, and we begin to spend our time standing on the vendor’s head nervously polling “how are we doing?” every day or two. Since Jonah Group is a services organization, we understand this dynamic all too well, and use two major strategies to prevent this from happening.
The first is Iterative Development and Delivery of vertically integrated pieces of the system (stories or use cases). I won’t go into this very deeply, because it is a well-developed, well-understood technique at the centre of modern Agile software development methods. Essentially this reduces risk by delivering working pieces of functionality early and often so that visibility into progress is re-established at discrete points in time (typically the end of each code Sprint).
The second is the process of continuously collecting answers to the question “How much time do you have remaining on this task?” from each of the team members. But how?
