Tips, Expertise, Articles and Advice from the Pro's for Your Website or Blog to Succeed
Some of the people I admire in the agile community avoid working with organizations that are not fully committed to the agile changes they are asking for.
This can create drama and a possible loss of connection between the ‘thought leaders’ and the rest of us. But what if some agile approaches would help us understand how best to support our clients if we do not have the full support of the organization?
Moving data from one system to another can be a complex process. In this post, we have broken down how to approach data migration in 3 stages:
Your requirements will take into consideration:
First Concern: Yes, We Want to Work!That's all we ask for; however, we are human beings, not a purchase order, not a slave, and not a claimant. Our work and motivation are to be of service to you because we find this noble and we want to bring you something.
There are two good and two bad reasons for hiring a consultant.
We all are aware that Agile software development has been in existence for about 18 years now, so it's clearly been enough time for organizations to adopt Agile processes for the complete development lifecycle.
But when it comes to writing contracts, I think most of us who have been working in software consulting companies will agree that there is still reluctance, and most of the time we either go back to waterfall language of writing or succumb to a mix of both the traditional and agile way.
Last month, I published the "Considering Offshoring? Consider These Lessons Learned" article, which provided five lessons that I have learned when attempting to employ offshore or nearshore services to assist with development efforts. One of those learned lessons reminded us that:
"Service providers exist to provide services for their clientele. At the core, they are doing it as a means to generate revenue."
As a reader of this article, one might pose the question...