(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
I am not one of the biggest Apple fan boy, but speaking truth I have been using their iPhone (thus iOS) for more than 5 years now. My first iPhone was iPhone 4.
Having said that, I am usually one of the consumers who would upgrade their devices on the very first day of it’s release of the newest iOS. To be honest, I have also been brave enough to run my iPhone with one of their BETA builds of iOS 5. Wasn’t a bad experience I should say.
Coming back to the iOS9, I was once again done with my first day upgrade and no issue noticed for the first 2 weeks untill one fine day my iPhone says that I haven’t backedup my iPhone for 2 weeks.
Strange. I use iCloud backup and it is supposed to auto-back up whenever I am Wi-Fi and charging.
I tried to manually press the “Back up Now” button but it would just not do anything. Another weird thing was that it also indicated my iPhone has NEVER been backed up but within “Manage Storage”, indicated that only 3 GB was left. I was like where is the other 2 GB gone.
Anyway, after numerous tries and going through suggestion on various forums I called up the Apple Support Customer number. Must say, I liked the call back option. The first executive was not very supportive and friendly. Was not able to help me and just ended up giving me the case ID and asked to call later.
Tried again after a week. This time, the fellow tried his best and even went to discuss the case with a “Senior Expert” (not sure what that means). Eventually, asked me to use the iTunes backup and sold the idea of purchasing more iCloud space. Good salesman skills :).
However, I was like I am not using much data to be backed up and quite sure that it’s way less than the free 5 GB.
Getting help from no official Apple support, I tried the following and am so glad that it worked like charm.
- Create a backup of iPhone manually on your computer using iTunes. See instructions here at: https://support.apple.com/en-us/HT203977
- Reset your iPhone to factory settings. https://support.apple.com/en-us/HT201274
- Setup you iPhone as a new Phone and DO NOT USE the backup option.
- AGAIN, Reset your iPhone to factory settings (Step 2).
- This time, use the backup from computer instead. See here: https://support.apple.com/en-us/HT204184
If everything goes well, you should have the backup working with iCloud.
E-iceblue Co., Ltd. is a vendor of .NET, Silverlight and WPF development components. The goal of e-iceblue is always to offer high-quality components for reading and writing different formats of office files.
Our components have been widely-used by most of the Fortune 500 corporations. The key developers of e-iceblue have over 10 years of combined experience developing high-performance, high-quality .NET, Silverlight and WPF component technology.
Everyday, e-iceblue products help a large number of developers from large/small companies in more than sixty countries to easier, better, faster and to be more productive develop and deliver reliable applications to their customers.
Using Spire.PDF for .NET to generate word document from PDF
A common use case over the years has been to convert the word documents in PDF documents for various obvious reasons. However, the opposite scenario has been relatively complex to implement.
Thanks to the new Spire.PDF for .Net, this can be really accomplished with relatively ease.
In this article, I will give a small walk-though on my thoughts and usage of this component.
To start with, you can download the Spire.PDF installation package from the link below. The installation is quite simple and professionally wrapped in a MSI. However, note that you don’t need to install this package on every server where you install your app using Spire.PDF.
Also, note that apart from the installer or a reference the Spire.PDF DLL, a valid license file is required.
At the time of writing this post, the price of various license is as follows. From the cost perspective, the return on investment is very high and this also provides you a support from the vendor. A win-win in my opinion.
Let’s start with a demo project. The first step is to include the reference to the Spire.PDF and License assemblies.
The interface of the component is very clear is self explanatory. Even without looking at any sort of documentation, I was able to write “3 line” program which can convert the PDF document to a word document. (or any other support format such as HTML, Image etc.)
Ok, now when we are ready with the program; let’s create a document with different elements such as Heading, Table and a paragraph.
The good news is that Spire.PDF does the 100% conversion keeping the output Word document same as the initial PDF document. 🙂
Overall, I was impressed by the power and ease provided by this product. While it didn’t always do everything in the way that I thought it should, it is probably due more to my lack of understanding of how the Word document model works rather than a flaw in this library. From a license and pricing overview, it’s not very expensive compared to other products in the markets which are offering the same functionality. Thus, a real value for money in my opinion.