Career Forums

 
  Modern Analyst Forums  Business and Sy...  Agile Analysis ...  What Does the Big Picture for Agile Projects Look Like
Previous Previous
 
Next Next
New Post 11/7/2011 10:30 AM
User is offline Tony Markos
493 posts
5th Level Poster


What Does the Big Picture for Agile Projects Look Like 

Hi all:

I am doing a little research here.   Question:  What does the up front big picture for an Agile project look like?   This is the artifact that would be used for scoping out a  system and to plan the various Agile iterations.

I got my own ideas, high level Data Flow Diagrams, but I am trying to understand what others think.

Tony

 
New Post 11/22/2011 8:45 AM
User is offline dldelancey
61 posts
8th Level Poster


Re: What Does the Big Picture for Agile Projects Look Like 

Are you asking about the "as-is" situation or the "as-it-should-be" situation?  I was recently frustrated with a project, trying to explain to someone that I needed time to build a big picture and was told "you have the statement of work, that's your big picture."  {heavy sigh}

 
New Post 12/29/2011 9:13 AM
User is offline Phyllis
1 posts
No Ranking


Re: What Does the Big Picture for Agile Projects Look Like 

 Tony Markos wrote
 

Hi all:

I am doing a little research here.   Question:  What does the up front big picture for an Agile project look like?   This is the artifact that would be used for scoping out a  system and to plan the various Agile iterations.

I got my own ideas, high level Data Flow Diagrams, but I am trying to understand what others think.

Tony

Explain the AS is and to be state.

 
New Post 12/29/2011 10:47 AM
User is offline Tony Markos
493 posts
5th Level Poster


Re: What Does the Big Picture for Agile Projects Look Like 

Didelancey:

Excellent question!  I purposefully did not address such in my question as I wanted to be as open to ideas as possible.  There are two schools of thought:

*   An "as is" is needed, and it is to be modified into the "to be".

*  An "as is" is a big  waste of time - so much so that such efforts often  kill a project.  Only create a "to be".

My thoughts:  Ideally, just create a "to be".   However, I have always found it to be the case that nobody - NOBODY - has a anywhere near the comprehensive, integrated understanding of what the "to be" is to be.   (That, by the way, is probably the reason why you got the silly response that you got - they are trying to blow you off because they do not want you to know that they can not help you.)  So, I always start with an "as-is".  

Note:  A good finished state "as is" is heavily focused on the unchanging business requirements  (i.e., the unchanging  "whats" vs the implementation specific  "hows").  So much that some experts say that a good "as is" is 98% of your "to be". 

Tony

 
New Post 8/2/2012 4:23 PM
User is offline ibtisam.jawad
15 posts
9th Level Poster


Re: What Does the Big Picture for Agile Projects Look Like 

For my projects, the initial big picture is just a list of business goals/drivers and a high level description of features/processes/tools that would support those in the "to be". May be a few diagrams that illustrate major functions. Later on, the team works to create desgin and architecture docs (often diagrams) that go along with the big picture.

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Agile Analysis ...  What Does the Big Picture for Agile Projects Look Like

 






 

Copyright 2006-2024 by Modern Analyst Media LLC