(Shrivastava & Date, 2010, p. 10) observed on various topics which are beneficial for the software development projects when the distributed teams are using agile methodologies. Sprint reviews could be an efficient method to enhance exterior communiqué while they assist to share data about the needs and feature dependencies amongst stakeholders. (Nilsson & Karlsson, 2014) also reiterated that agile practices such as sprint review and retrospectives are also team ceremonies, which, if performed properly, could address some of the challenges in communication. In the sprint review the project team will have an opportunity to gather feedback from the customer and other stakeholders on a regular basis and at short intervals. Customer requests for changes in requirements and priorities for the next iteration can also be communicated to the team.
(Shrivastava & Date, 2010, p. 10) also studied the impact on trust and confirms that use of agile frameworks can also help in generating trust between people of different cultures involved in the process by regular communication and delivery of software.
(Paasivaara & Lassenius, 2006, p. 4) further analyzed the impact on customers, business when using agile in distributed teams and stated that from customer’s point of view this way of software development and implementation provides extra flexibility when the customer is able to ask for changes during the development phase without having a lot of time-consuming discussions with subcontractors. Further, the customer establishment gets empowered to introduce subcontractors into the assignment already in the initial stages of growth, when the customer is not yet able to define the requirements in a detailed manner but can only rely on early correction of direction when needed.
When implementating agile within the organizations and especially in context of Distributed Teams; it is vital to look at the possible theories and literature available on the topics.
Software development methodologies are constantly evolving due to changing technologies and new demands from users (Nerur, et al., 2005, p. 73). Current vibrant business atmosphere has produced evolving establishments that constantly acclimates their arrangements, approaches, and rules to suit the fresh atmosphere.
(Rigby, et al., May 2016, p. 49) also argued that agile is efficient, effective and easiest to implement under circumstances generally originating in software innovation. The problem to be solved is significantly complex; solutions are primarily unidentified, and product requirements will most probably change; the work can be modularized; close partnership with end users (and swift response from them) is achievable; and creative teams would typically outperform command-and-control groups.
The Right Conditions for Agile
(Rigby, et al., May 2016, p. 50) called out the reason for failure in organizations and argued that large companies typically launch change programs as massive efforts. However, the smaller introductions of agile are normally the more successful ones. These introductions frequently start in IT as here the software developers are conversant in the principles. Later agile could move on to different functions, with the original users act like coach. On the other hand (Rigby, et al., May 2016) summarized the key issues when migrating to agile in an organization. Keeping these high-level key issues not only will help organizations to implement agile within their teams but also enlists the wide array of expertise, topics involved in such an execution.
(Boehm, 2002) specified that IT inclinations are shifting us nearer to agile approaches’ evolving needs and speedy alteration home-ground features, growing reliability issues require methods which could be established with plan-focused resolutions. Hence, the organizations should cautiously move towards the optimum balance of plan-focused methods and agile methods that fit their circumstances and fulfill their disparate requirements.
Key issues when migration to agile
Time flies and before you know it’s time to start working on your new year resolutions for your next year.
I still have few of them from my last year in my ToDo list, so not much to work on that area this year.
Again, wish you world of happiness now, and throughout the seasons of the coming year 2015.
As usual, JetPack release the yearly report for this blog. And to be honest, it’s been a great year specially for my blog. I got some time spend on writing on a range of topics from technology to management.
Here are some excerpts from the report:
The concert hall at the Sydney Opera House holds 2,700 people. This blog was viewed about 32,000 times in 2014. If it were a concert at Sydney Opera House, it would take about 12 sold-out performances for that many people to see it.
That’s 148 countries in all! Most visitors came from The United States. India & U.K. were not far behind.
According to Wikipedia, Daylight saving time (DST) or summer time is the practice of advancing clocks during the lighter months so that evenings have more daylight and mornings have less. Typically clocks are adjusted forward one hour near the start of spring and are adjusted backward in the autumn.
And how many times we have seen that how this concept has created troubles for not only small software but also for giants. iOS for iPhone and iPad has already been culprit for having some nasty bugs related to this. And it was rumored that they have done the same mistake again in their latest iOS 7 as well.
Anyway, this post is not about Apple so let me come straight to what I found. I ordered a few books from Amazon UK around 10 days back and was expecting delivery anytime. When I checked the order status yesterday (29th March 2014), the status on the web site showed that the package is in transit (Amsterdam) and has been out for delivery on 29 March 2014 9:49:17.
That’s another story that I am still waiting for my package to me received. This triggered me to check the status again today (on 30th March 2014) and this is what I saw.
Basically, the same message but the time stamp was shifted 1 hour back. That is simply a programming error where they converted the time of out for delivery because of DST. But that’s not how it should be, at least in my opinion.
Not something which Amazon needs to take real action on but they might want to look at it.
And btw, @Amazon do I get a free gift card for finding this bug in your system? J