Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  General  Selecting ISDMs
Previous Previous
 
Next Next
New Post 4/22/2015 10:45 PM
User is offline Jaco Viljoen
1 posts
No Ranking


Selecting ISDMs 
Modified By SuperUser Account  on 4/23/2015 1:42:19 PM)

Good day

I am well aware of the workload of Systems Analysts, but when selecting the correct Information System Development Methodologies (ISDMs) for different projects, time could be wasted with the selection process. 

I am busy with research into the selecting of ISDMs. No ISDM are fit for every project, and therefore there should be a selection for the right ISDM (please see the cover letter explaining the research conducted at http://goo.gl/1aXjAU ). A framework will be constructed from this research to guide the selection of the ISDM to be used in a project. This survey gives you an opportunity to impact the framework of selecting ISDMs: http://goo.gl/forms/upKkz4C2jD

I would really like to get your opinion and I appreciate your valuable time.

Kind regards
Jaco Viljoen
 
New Post 4/23/2015 1:49 PM
User is offline NitWitNick
259 posts
5th Level Poster


Re: Selecting ISDMs 

 "The Information Systems Development Methodology (ISDM) is designed to provide a consistent, repeatable process for developing systems. By referencing, utilizing and applying the techniques within this methodology, development teams have a standard framework necessary to efficiently and effectively scope a project, conduct analysis, define and design the solution, create the system modules and evaluate the system after its implementation."

"customer needs analysis
scope definition
requirements analysis
design
development
integration/test/acceptance
implementation-deployment"

 

Here is some stuff ...

http://www.myfloridacfo.com/division/dis/isdm/#.VTlLdPD-kyl 

 
New Post 4/25/2015 10:20 PM
User is offline Kimbo
450 posts
5th Level Poster


Re: Selecting ISDMs 

Hi Jaco,

Very hard to be so prescriptive when every project is different. There are often common elements but its a waste of time doing things just for the sake of it. Whatever your ISDM is you should have the power to pick the bits that make sense for that project.

Kimbo

 
New Post 11/30/2015 7:25 AM
User is offline Victor Chase
7 posts
10th Level Poster


Re: Selecting ISDMs 

To be practical, and to be able to estimate well, one needs to bear in mind the history, the ethos and the existing expertise available to the project.  Yes, some methodologies are better for high-risk vs low-risk projects, or for winning an air-traffic control or defense contract vs a wedding planner solution.  But normally one will find it very difficult to use a different methodology per project unless one is assembling a new team per project and the business is for some reason open to that kind of change from project to project.

In my experience, one needs to understand of a couple of methodologies as 'cook-book'; but in understanding its tools and techniques, bring your toolbox of methods and techniques and create a (self checking) methodology that fits with the project and the team involved.

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  General  Selecting ISDMs

Community Blog - Latest Posts

Rajesh-N
Rajesh-N
What Everyone Must Know about AI in Testing Artificial Intelligence is the buzzword that we frequently keep hearing. Its widespread popularity and influence can be understood from the way industries adopting AI in their organization. Whether it’s Healthcare, Automobile, Banking & Financial Services, or Airlines, many industries have st...
0 Responses
Ashish Adike
Ashish Adike
As a Business Analyst, very often we get into a situation where the Project requires multiple IT Products to be evaluated before implementation and might seek Business Analyst’s recommendation for the same. With the ever-growing range of Products in the market and the marketing promotions associated with some of the products, it’s very ...
0 Responses
m_anst
m_anst
What Does Success Look Like? I challenge Business Analysts to view requestors’ requirements as an opportunity to define success. Too often, teams fall into a trap focused on requestors’ prescriptive requirements that are meant to serve as roadmaps for developers and testers. When you limit your view of requirements to this prescripti...
0 Responses






Latest Articles

The Art of Letting Stakeholders Have Your Way
Nov 23, 2020
0 Comments
Study after study in behavioral science show that certain approaches are more effective than others when we’re trying to convince others to see ...
Copyright 2006-2020 by Modern Analyst Media LLC