We’re often asked by companies about how they can get the most value from Agile/Scrum practices. More specifically, they want to know if they are being as effective as best they possibly can be by using the Scrum framework for their explicit needs.

The other objective for individuals is determining if it necessary to be certified in order to be effective in the Agile Scrum world?   In short, a good Scrum Master must understand four things: the business they work in, the technology they work with, the Agile and Scrum principles, and, most importantly, people!  Based on these facts, Scrum Master Certification is not enough – real life experience and a bit of soft skills should be part and parcel of their training. For organizations, the main goal is to understand industry best practices when adopting and applying agile principles, to build strong teams, understand and distill business needs into software requirements.

In terms of getting a good grip on training for Agile/Scrum, one can opt to pursue a certification in Scrum (CSM) Certified Scrum Master for personal reasons or for a job requirement. Or, one can simply opt to learn the benefits and pitfalls of the methodology and decide the best approach for them.

There are different ways to get started with Agile training. Below are two of the most common paths to Agile our students take.

Jeff Nelson, a former Googler and inventor of Chromebook says on Quora, “One habit I've clung to is writing small prototypes when I'm trying to learn new concepts.
For example, I'll sit down with a book or a web page, and over the course of a few hours, write 30 or 40 programs all of them only a few dozen lines long.  Each program intended to demonstrate some simple concept. This prototyping makes it very easy to try out many concepts in a short period of time.”

Miguel Paraz, Software Engineering Student habit is to “keep a log in a text file or document on my work computer. Before trying to solve a problem, I write it down first. And then I describe the details as they happen.”

There are normally two sides to the story when it comes to employment. On one hand, employers hold the view that the right candidate is a hard find; while on the other, job hunters think that it’s a tasking affair to land a decent job out there.

Regardless of which side of the divide you lay, landing good work or workers is a tedious endeavor. For those looking to hire, a single job opening could attract hundreds or thousands of applicants. Sifting through the lot in hope of finding the right fit is no doubt time consuming. Conversely, a job seeker may hold the opinion that he or she is submitting resumes into the big black hole of the Internet, never really anticipating a response, but nevertheless sending them out rather than sit back doing nothing.

A recruitment agency normally keeps an internal database of applicants and resumes for current and future opportunities. They first do a database search to try and identify qualified and screened candidates from their existing crop of talent. Most often the case, they’ll also post open positions online through industry websites and job boards so as to net other possible applicants.

When it comes to IT staffing needs, HR managers even find a more challenging process in their hands. This is because the IT department is one of the most sensitive in any given organization where a single slip-up could be disastrous for the company (think data security, think finances when the IT guys are working in tandem with accounts). You get the picture, right?

As part of our Java Tutorials program, we will list a number of interview questions to aid in a better understaing of Java and J2EE and, hopefully, provide a greater likelihood of getting a job.  Let us begin with the basics:

1. What is meant by J2EE?

J2EE is an abreviation for Java 2 Platform Enterprise Edition

2.  What is the purpose of J2EE?

The purpose of J2EE is to provide a component based platform in a multitier application model with transaction management, web services and reusable component support.

3.  What is the tier structure of the typical J2EE application?

A typical J2EE application consists of the following tiers/machines:  the client machine (browser/non-browser application), the J2EE server (an application server such as Oracle, JBoss, GlassFish, Tomcat) and a database.