|
 |
| Articles and White Papers
|
|
|
|
|
|
|
|
Entries for the 'SDLC, Process, and Methodologies' Category
» FEATURED: Integrating and Understanding Standard Business Analysis Methodologies To Develop New Technology Hybrids
 (1988 Views)
( 0 Comments)
| Across North America, businesses in all sectors are adopting standard development methodologies to turn out a higher quality of goods and services. The tried and true approaches that have yielded such great results for competitors are heralded as best practices. But here is the sad news: no one methodology fits all. In fact, different methodologies... |
» FEATURED: Agile Business Analysis: Interview with Scott Ambler
 (5843 Views)
( 17 Comments)
| Whether you’ve never heard of Agile or you just finished your nth Agile project, you need to understand that Agile is here to stay! Are you, the Business Analyst, an extinct species in this new world? Is your career changing? Do you need new skills?
Agile guru and visionary Scott Ambler talked with Adrian Marchis, ModernAnalyst.com's Publishing Ed... |
» FEATURED: How to Be an Agile Business Analyst
 (1784 Views)
( 0 Comments)
| A question was asked in the Modern Analyst forums. I paraphrase:
"How does a BA do their work in an Agile project? Can you give some practical examples?"
I've thought quite a bit about this topic and have experience with BAs on agile developments as a project manager and business analyst.
As a project manager I get frustrated by (but... |
» Volere Requirements Techniques: an Overview
(993 Views)
( 0 Comments)
| The Volere requirements techniques were developed to answer the need for a common language for discovering requirements and connecting them to solutions. The language needs to be understandable by business people, customers, business analysts, engineers, designers, suppliers, testers or anyone else whose input is needed. All of these people have di... |
» Current Systems Analysis
(704 Views)
( 0 Comments)
| The subject of current systems analysis is usually greeted with dismay or disdain by systems departments. There are many reasons for this. In many installations, the support of current systems takes more than 85% of the systems department's time, and the departments are more than ready to get on with new systems development and bury the old, non-wo... |
» System Design Backwards
(526 Views)
( 0 Comments)
| One of the biggest challenges in any system design effort is to produce a viable design that is well thought-out with all of the pieces and parts working harmoniously together. If something is forgotten, regardless of its seeming insignificance, it will undoubtedly cause costly problems later on. The task, therefore, is to produce a design that is ... |
» Stepwise Refinement
(464 Views)
( 1 Comments)
| In a nutshell, the concept of "stepwise refinement" is to take an object and move it from a general perspective to a precise level of detail. Architects have used such an approach for years, as have engineers building products. But to do so, they realized they cannot simply go from the general to the specific in one felled swoop, but instead, in in... |
» Why I.T.Standards Fail
(430 Views)
( 0 Comments)
| Not long ago Shane "Locutus" Shields wrote an interesting blog entitled, "What is the use of standards?" whereby he expressed his disillusionment with standards in the Information Technology (I.T.) field. His discontent is not without precedence. Most of us have at one time or another yearned for standards in our work effort, only to be thwarted by... |
» Is PRIDE too rigid?
(434 Views)
( 0 Comments)
| I was recently asked by an "Agile" proponent if I thought our "PRIDE" methodologies were too rigid for today's fast-paced Information Technology world, that perhaps it was too bureaucratic. First, I pointed out that "PRIDE" was more of a way of thinking as opposed to anything else. You can remove all of the documentation associated with the methodo... |
» Requirements for My New Car: a Fable (A Case for gathering and eliciting requirements collaboratively)
(1916 Views)
( 8 Comments)
| A lot of IT folks and or BA’s believe that if you create the requirements without the business, and then review the requirements with the business for confirmation, you can save a lot of time.
After all, creating requirements collaboratively just takes too long, and the business doesn't know what they want, anyways. In addition, we (IT or BA) k... |
|
 |
|
|