Software and IT Development

Software and IT Development

Case Study 11.1: It’s an Agile WorldThis case illustrates a common problem in software and IT development, where programmers and IT staff are anxious to lock in specifications as early as possible so they can “get to work” without having to worry about invasive or disruptive input from the end users. Unfortunately, what typically happens is that the finished product is not what the users needed or thought they needed and a long list of fixes and modifications are needed to make it work correctly. This case is based on a true story in a hospital IT department that routinely struggled with these sorts of user conflicts until they sifted to an Agile methodology.Questions

Why does the classic waterfall project planning model fail in this situation? What is it about the IT department’s processes that leads to their finished systems being rejected constantly?
How would an Agile methodology correct some of these problems? What new development cycle would you propose?
Why are “user stories” and system “features” critical components of an effective IT software development process?
Using the terms “Scrum,” “Sprint,” and “User stories,” create an alternative development cycle for a hypothetical software

 

Create an order via https://peakassignments.com/order if you need work on such topic and many more from different disciplines.

Grading Rubric for Writing Assignment

Your professor may use a slightly different rubric, but the standard rubric at AUR will assess your writing according to the following standards:

 

 

	A (4)	B (3)	C (2)	D/F (1/0)
Focus: Purpose	Purpose is clear	Shows awareness of purpose	Shows limited awareness of purpose	No awareness
Main idea	Clearly presents a	There is a main idea	Vague sense of a	No main idea
	main idea and	supported throughout	main idea, weakly
	supports it	most of the paper.	supported
	throughout the		throughout the
	paper.		paper.
Organization:	Well-planned and	Good overall	There is a sense of	No sense of
Overall	well-thought out.	organization, includes	organization,	organization
	Includes title,	the main	although some of the
	introduction,	organizational tools.	organizational tools
	statement of main		are used weakly or
	idea, transitions and		Missing
	conclusion.
Organization:	All paragraphs have	Most paragraphs have	Some paragraphs	Para. lack clear ideas
Paragraphs	clear ideas, are	clear ideas, are	have clear ideas,
	supported with	supported with some	support from
	examples and have	examples and have	examples may be
	smooth transitions.	transitions.	missing and
			transitions are weak.
Content	Exceptionally well-	Well-presented and	Content is sound and	Content is not sound
	presented and	argued; ideas are	solid; ideas are
	argued; ideas are	detailed, developed	present but not
	detailed, well-	and supported with	particularly
	developed,	evidence and details,	developed or
	supported with	mostly specific.	supported; some
	specific evidence &		evidence, but
	facts, as well as		usually of a
	examples and		generalized nature.
	specific details.
Research (if	Sources are	Sources are well	Sources support	The paper does not
assignment	exceptionally well-	integrated and	some claims made in	use adequate
includes a	integrated and they	support the paper’s	the paper, but might	research or if it does,
research	support claims	claims. There may be	not be integrated	the sources are not
component)	argued in the paper	occasional errors, but	well within the	integrated well.
	very effectively.	the sources and	paper’s argument.	They are not cited
	Quotations and	Works Cited conform	There may be a few	correctly according
	Works Cited	to MLA style sheet.	errors in MLA	to MLA style, nor
	conform to MLA		style..	listed correctly on
	style sheet.			the Works Cited
				page.