1. Explain why the rapid delivery and deployment of new systems is often more im
ID: 3888531 • Letter: 1
Question
1. Explain why the rapid delivery and deployment of new systems is often more important to businesses than the detailed functionality of these systems.
2. To reduce costs and the environmental impact of commuting, your company decides to close a number of offices and to provide support for staff to work from home. However, the senior management who introduce the policy are unaware that software is developed using Scrum. Explain how you could use technology to support Scrum in a distributed environment to make this possible. What problems are you likely to encounter using this approach?
Explanation / Answer
Hi,
Advantages of rapid delivery and deployment of new systems-
1. Rapid delivery is an approach in which the company prioritizes its features and selects the critical set of features and then develop then first and then deploy to the production. This approach yields the final product in the very short time to the market.
2. As the final product is produced in lesser time duration, it can help organizations gain competitive advantage over others.
3. Short cycles help the customer build trust on software development organizations.
4. Another essential concept within continuous delivery is that of shared dev and ops visibility. The right process ensures both sides have visibility into an application’s behavior as it moves from testing into production.
How Technology Support Scrum for distributed teams ?
a) Communication Methods: The traditional scrum framework requires your team to meet for the daily scrum. We have various modes including Skype for Business, Skype, Google Hangouts, Slack or any other system you prefer. We also install version control systems based on your requirements (e.g. GIT, SVN, TFS, Jira, etc.).
b) Rotation of Duties Every Sprint: During one sprint, you’ll likely have some developers focus on bugs and other focus on implementing tasks (a.k.a. features). Before the next sprint begins, team roles can change so nobody is bored and everyone has the chance to develop different skills. This doesn’t have to apply exclusively to developers: QA testers, for example, can trade between manual and automated testing.
c) Task Assignment: We can use Scrum tools like JIRA, Hansoft, Scrumpy etc .Upon the approval of technical leads, tasks are distributed to team members based on their abilities and strengths. We can track the progress of the activities using the sprint burn down charts and we can calculate the velocity of the sprint. This allows the remote team to leverage the different skills of its programmers. In other words, every team member brings the best of his or her abilities to contribute to the project.
Problems in this approach-
1. Difficulty to monitor and the tasks and the Progress.
2. No authenticity of work being done
3. No liability of the work being done.
4. Different time zones and conflicting working hours impact communication and collaboration.
5. Cultural and language differences impact communication and collaboration.
6. An effective tool chain is needed for requirements repositories, SCM, management, build and deployment setup, defect tracking, and project management tools.
4. Lack of communication among team members.
5. Face to face communication proves to be faster in issue resolution.
6. There will be lack of healthy work culture between the employee and employer.
Related Questions
Navigate
Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.