Good Problems In Software Development Essay Example

Type of paper: Essay

Topic: Software, Business, Development, Improvement, Programming, Advancement, Community, Venture Capital

Pages: 9

Words: 2475

Published: 2021/01/04



Software sways all of us, consequently software improvement issues as well and Value has moved to software and information. An ordinary application incorporates numerous associated parts, for example, administrations, coordination layers, legacy frameworks, databases and outsider or Cloud-based administrations. The capacity to scale dexterous software advancement to huge associations has dependably had doubters. The always expanding demand of software in business, industry, organization, diversions and explores have made software building and advancement more perplexing. This requires the requirement for more elevated amount deliberation of software frameworks keeping in mind the end goal to grow true frameworks that meets the new difficulties confronting software building and improvement process. The term software development faces number of issues that highlight the requirement for changes in our current ways to software advancement. Every new innovation change offered new and frequently better ways to the unpredictability of the software improvement process. Common contentions are that agile works for little software improvement gathers yet not for huge ones (Highsmith, 2002). Following are the few problems faced in software development:


Today's software applications must be produced and incorporated speedier than any time in recent memory by uniting assorted, conveyed components owned and constructed by various groups. While individual discharge cycles for these segments are getting to be shorter, the rate of progress and general many-sided quality of the software life cycle has expanded. This makes new stresses that are not tended to by existing application improvement forms.

Agile is not ready for automated testing

The fast conveyance cycles under coordinated make software to computerize testing a need to keep the nature of the item and the code from slipping. The expense of embracing robotized testing and the bother in changing methods for attempting to suit it can appear to be more trouble than they're worth. In any case neglecting to present computerized testing makes it dubious for manual testing groups to continue top of bugs amid the short conveyance times for cycle of the software - especially as the general code develops in size (Heath, 2012).

Hard to get acquired

For organizations with a long history of creating software utilizing option procedures, changing to coordinated obliges a significant change in the path everybody from software support groups to administration work. Yet individuals are animals of propensity and getting the support group to drop their requests for a library of documentation isn't simple. Getting everybody included in a task to see how they and their associates can function and alleviate hazard without broad documentation to fall back on will take quite a while - for instance, on account of the Welcome Trust it took year and a half. Time responsibilities can likewise be burdensome both for designers and business clients. The IT group and whatever remains of the business will must be arranged to give consistent pieces of time to examining venture prerequisites and results, which they have to fit in the day by day requests of the occupation (Heath, 2012).

Ignores the creative nature of coding

Commentators of the agile development claim it epitomizes a more extensive issue with software improvement systems, that the emphasis on methodology disregards the inventive way of programming. Development in Software is more similar to making a motion picture than building autos on a get together line.With these methods and procedures, individuals need to take software designers, say they are all made equivalent, and place them on a methodology, turn a wrench and software will turn out, But software is a unique case. It isn't a result of a sequential construction system. We have to perceive the outline and imagination that goes into it. This attention on methodology overlooks how vital configuration choices are when creating software. In software improvement, outline choices focus everything from to what extent it’s going to take to add to the software, to how great the client experience will be (Heath, 2012).

Operational challenges

Operational difficulties are less novel to software advancement and accordingly less said yet just as if not more hard to handle. Managing administration, professional success, and distinguishment, cooperation with different specialists and also creators and item supervisors, and constant instruction of both specialized and business parts of an association are all issues that software engineers face. Truly, the accentuation of the unadulterated specialized difficulties above makes light of these operational difficulties.

Poor communications

It is critical to keep everybody insider savvy on task status. However it is anything but difficult to neglect to do it. This is the place a considerable measure of the doubt in the middle of IT and the business group originates from: The business does not feel like it has a decent handle on what's occurring with its anticipates. Furthermore, the more it feels left oblivious, the more probable it is to begin attempting to micromanage or power things to happen the way it feels it ought to be carried out. Engineers can alleviate this issue by telling individuals where things stand, both all the time and when breakthroughs are proficient, or the status changes.

Absence of the joint effort

As a software improvement groups extend quickly to keep pace with the exponential development of software-escalated items, the test to empower these bigger and regularly all inclusive conveyed groups to cooperate all the more effectively can be overwhelming. The absence of coordinated effort and permeability often brings about the making of incorrect or copy information, further obstructing the benefit of the group. Also, with groups utilizing distinctive apparatuses, techniques and procedures while depending on different information sources, it’s about difficult to reuse demonstrated models, code and tests viably.

Agile Methodology Contenders

The different agile techniques impart a great part of the same reasoning, and additionally a considerable lot of the same attributes and practices. Be that as it may from a usage viewpoint, each has its own particular formula of practices, phrasing, and strategies. Here we have condensed a couple of the principle light-footed software advancement approach contenders:


Scrum is a lightweight, agile task administration structure with expansive materialness for overseeing and controlling iterative and incremental activities of various kinds. Ken Schwaber, Mike Beedle, Jeff Sutherland and others have contributed fundamentally to the development of Scrum in the course of the most recent decade. Scrum has earned expanding fame in the lithe software improvement group because of its straightforwardness, demonstrated gainfulness, and capacity to go about as a wrapper for different building practices advanced by other dexterous systems.
With Scrum strategy, the "Item Owner" meets expectations nearly with the group to distinguish and organize framework usefulness in manifestation of an "Item Backlog". The Product Backlog comprises of highlights, bug fixes, non-utilitarian necessities, and so forth - whatever needs to be carried out to effectively convey a working software framework. With needs determined by the Product Owner, cross-useful groups gauge and sign-up to convey "conceivably shippable additions" of software amid progressive Sprints, normally enduring 30 days. When a Sprint's Product Backlog is conferred, no extra usefulness can be added to the Sprint aside from by the group. When a Sprint has been conveyed, the Product Backlog is examined and reprioritized, if important, and the following arrangement of usefulness is chosen for the following Sprint. Scrum system has been demonstrated to scale to different groups crosswise over extensive associations with 800+ individuals (Greer & Hamon, 2011).

Lean and Kanban Software Development

Lean Software Development is an iterative dexterous philosophy initially grown by Mary and Tom Poppendieck. Incline Software Development owes a lot of its standards and practices to the Lean Enterprise development and the acts of organizations like Toyota. This Lean Software centers the group on conveying Value to the client.The principle standards of Lean strategy include:

Dispensing with Waste

Enhancing Learning
Choosing as late as could be expected under the circumstances
Conveying as fast as could be expected under the circumstances
Enabling the Team
Building Integrity In
Seeing the Whole
Building Integrity In
Seeing the Whole
Incline technique disposes of waste through such practices as selecting just the really profitable highlights for a framework, organizing those chose, and conveying them in little groups. It underlines the velocity and productivity of advancement work process and depends on quick and solid criticism in the middle of software engineers and clients. Lean uses the thought of work item being "pulled" by means of client solicitation. It centers choice-making power and capacity on people and little groups since examination demonstrates this to be speedier and more proficient than progressive stream of control. Incline likewise focuses on the productivity of the utilization of group assets, attempting to guarantee that everybody is gainful, however, much of the time as could be expected. It focuses on simultaneous work and the least conceivable intra-group work process conditions. Incline additionally firmly suggests that robotized unit tests be composed in the meantime the code is composed (Greer & Hamon, 2011).
The Kanban Method is utilized by associations to deal with the production of items with an accentuation on consistent conveyance while not overburdening the improvement group. Like Scrum, Kanban is a methodology intended to help groups cooperate all the more successfully. Kanban is in the light of 3 fundamental standards:

Picture what engineers do today (work process): seeing all the things in setting of one another can be extremely enlightening

Limit the measure of work in the advancement (WIP): this helps adjust the stream-based approach, so groups wear 't begin and focus on an excessive amount of work on the double

Improve stream: when something is done, the following most astounding thing from the build-up is maneuvered into play

Kanban advances persistent cooperation and supports dynamic, continuous learning and enhancing by characterizing the best conceivable group work process. Perceive how VersionOne bolsters Kanban software advancement.

Extreme Programming (XP)

XP, initially portrayed by Kent Beck, has developed as a standout amongst the most mainstream and questionable lithe systems. XP is a restrained way of conveying top notch software rapidly and consistently (Greer & Hamon, 2011). It advances high client association, fast criticism circles, persistent testing, nonstop arranging, and close cooperation to convey working software at exceptionally visit interims, commonly every 1-3 weeks.
The first XP formula is in the light of four basic qualities – straightforwardness, correspondence, input, and fearlessness – and twelve supporting practices:

Arranging Game

Basic Design
Pair Programming
Test-Driven Development
Nonstop Integration
Aggregate Code Ownership
Coding Standards
Concerns In Agile Versus Plan-Based Software Development
The Agile system proposes an incremental and iterative way to programming configuration. It was basically grown in light of the constraints of Plan-based, as an approach to give creators more opportunity. The outlined procedure is broken into individual models that creators take a shot at. There is no foreordained strategy or arrangement with the agile system. Rather, creators are allowed to react to changes in prerequisites as they emerge and roll out improvements as the venture advances. Agile is a pretty new player to the improvement diversion. Notwithstanding, it has made considerable picks up being used and the prevalence in the last couple of years. As a matter of first importance, before developers set out on a product configuration undertaking, verify developers have the fundamentals of the programming plan down. Developers may need to investigate this extraordinary web advancement accreditation course to sharpen their aptitudes. Once, they’ve got this secured; developers may be pondering which strategy is a good fit for developers and their task. Before settling on a decision, it is vital to do some exploration and comprehend the preferences and restrictions of every methodology. We should take an inside and out take a gander at the upsides and downsides of both the Agile and Plan-based techniques for programming improvement (Martin, 2003).
Agile may be portrayed as freeform programming outline. Programming designers chip away at little modules at once. Client input happens all the while with improvement, as does programming testing (for more data about programming testing, examine this product testing course). This has various preferences, particularly in venture situations where advancement needs to have the capacity to react to changes in necessities quickly and successfully.
Agile can be particularly useful in circumstances where the finished objectives of undertakings are not obviously characterized. For instance, in the event that developers are working with a customer whose needs and objectives are a touch foggy, it is most likely beneficial to utilize the agile technique. The customer's prerequisites will probably continuously illuminate as the task advances, and improvement can undoubtedly be adjusted to meet these new, developing necessities. Agile is likewise a fantastic choice for exploratory programming outline (Holmström, Fitzgerald, Ågerfalk & Conchúir, 2006).
Finally, this system likewise encourages connection and correspondence – cooperation is more imperative here than outline. Since the connection among distinctive originators and partners is key, it is particularly helpful for collaboration arranged situations. Diverse designers take a shot at distinctive modules all through the advancement methodology and after that work to incorporate these modules together into a strong bit of programming toward the end of the undertaking. On the off chance that developers think Agile may be ideal for their next venture, look at this incredible prologue to agile course.
The accentuation of Plan-based is the venture arrange and subsequently before starting any sort of improvement their requirements to be an unmistakable arrangement and a reasonable vision in place. Since the Plan-based strategy requires forthright, far-reaching arranging, developers can dispatch programming decently fast. Developers can likewise assess timetables and plans all the more precisely, which unquestionably has a tendency to please customers.
Besides, Plan-based advancement courses of action have a tendency to be more secure in light of the fact that they are so plan situated. Case in point, if an architect drops out of the venture it isn't a tremendous issue, as the Plan-based system obliges far-reaching arranging and documentation. Another fashioner can without much of a stretch take the old creator's spot, taking the improvement arrangement without an issue (Boehm & Turner, 2003).
In spite of the fact that very adaptable, Agile basically doesn't have the structure that the Plan-based system has and this does show a few disadvantages. Agile tasks have a tendency to be difficult to anticipate, from courses of events to plans. Without a solid arrangement, everything remains a touch ambiguous and undefined.
Also, as already talked about, dynamic client association and extreme joint effort are needed all through the Agile methodology. This can demonstrate exceptionally risky for various reasons. As a matter of first importance, this technique for improvement can be truly time intensive, substantially more tedious than the Plan-based system. Furthermore, it implies that creators need to be conferred for the length of time of the venture. On the off chance that a fashioner leaves amidst a Plan-based technique advancement venture, it likely won't be too enormous of an arrangement as the task is arrangement based. On account of the agile strategy, on the other hand, improvement is a great deal more individual based. Having a man drop out of the venture could demonstrate disastrous (Petersen & Wohlin, 2010).
The Plan-based strategy is unimaginably inflexible and rigid. Adjusting the venture outline at any stage in the undertaking can be an aggregate bad dream, and once a stage has been finished, it is almost difficult to roll out improvements to it. Along these lines, in case one wants to utilize Plan-based, developers will need to accumulate the greater part of the necessities forthright. Moreover, the issue with the Plan-based technique is that criticism and testing are conceded until late into the venture. So if there is an issue, it is extremely hard to react to it, obliging a generous measure of time, exertion (Petersen & Wohlin, 2010).


Boehm, B., & Turner, R. (2003). Using the risk to balance agile and plan-driven methods. Computer, 36(6), 57-66.
Heath, N. (2012). Agile development: Five ways it can trip developers up. TechRepublic. Retrieved 27 March 2015, from
Highsmith, J. (2002). Agile software development ecosystems. Addison-Wesley Longman Publishing Co., Inc..
Holmström, H., Fitzgerald, B., Ågerfalk, P. J., & Conchúir, E. Ó. (2006). Agile practices reduce distance in global software development. Information Systems Management, 23(3), 7-18.
Martin, R. C. (2003). Agile software development: principles, patterns, and practices. Prentice Hall PTR.
Greer, D., & Hamon, Y. (2011). Agile software development. Software: Practice and Experience, 41(9), 943-944.
Petersen, K., & Wohlin, C. (2010). The effect of moving from a plan-driven to an incremental software development approach with agile practices. Empirical Software Engineering, 15(6), 654-693.

Cite this page
Choose cite format:
  • APA
  • MLA
  • Harvard
  • Vancouver
  • Chicago
  • ASA
  • IEEE
  • AMA
WePapers. (2021, January, 04) Good Problems In Software Development Essay Example. Retrieved April 24, 2024, from
"Good Problems In Software Development Essay Example." WePapers, 04 Jan. 2021, Accessed 24 April 2024.
WePapers. 2021. Good Problems In Software Development Essay Example., viewed April 24 2024, <>
WePapers. Good Problems In Software Development Essay Example. [Internet]. January 2021. [Accessed April 24, 2024]. Available from:
"Good Problems In Software Development Essay Example." WePapers, Jan 04, 2021. Accessed April 24, 2024.
WePapers. 2021. "Good Problems In Software Development Essay Example." Free Essay Examples - Retrieved April 24, 2024. (
"Good Problems In Software Development Essay Example," Free Essay Examples -, 04-Jan-2021. [Online]. Available: [Accessed: 24-Apr-2024].
Good Problems In Software Development Essay Example. Free Essay Examples - Published Jan 04, 2021. Accessed April 24, 2024.

Share with friends using:

Related Premium Essays
Contact us
Chat now