FOLLOW CASE STUDY: REMOTE DEPOSIT CAPTURE
Q1:
* COMPARISON BETWEEN WATERFALL AND AGILLE.
! WATERFALL: (UGH, TERRIBLE NAME !), COULD BE CALLED MORE PROPERLY A
'TRADITIONAL ' APPROACH .
! AGILE : A NEWER, SPECIFIC TYPE OF RAPID APPLICATION DEVELOPMENT THAN
WATERFALL , BUT NOT NEW , THAT IS TYPICALLY DEPLOYED IN SCRUM.
WATERFALL METHOD
! SOME PROBLEMS WE ENCOUNTERED WHEN USING WATERFALL
! WATERFALL METHOD
ONE AREA THAT IS ALMOST ALWAYS MISSING IS THE EFFECTIVENESS OF REQUIREMENTS .
GATHERING AND DOCUMENTING REQUESTS IN A WAY THAT MAKES SENSE TO THE
CUSTOMER IS OFTEN THE MOST DIFFICULT PART OF SOFTWARE DEVELOPMENT , IN MY
OPINION . T HE CLIENT IS SOMETIMES INTIMIDATED BY THE SPECIFICS AND DETAILS ,
WHICH ARE PROVIDED EARLY ON IN THE PROJECT , THAT ARE IMPERATIVE WITH THIS
APPROACH . ADDITIONALLY , THE CUSTOMER CANNOT ALWAYS VISUALIZE THE
APPLICATION FROM THE REQUIRED DOCUMENT . W IREFRAME AND MOCKUP CAN HELP , BUT
THERE'S NO QUESTION THAT MOST END USERS HAVE TROUBLE PUTTING THESE ELEMENTS
TOGETHER WITH WRITTEN REQUIREMENTS TO GET A GOOD PICTURE OF WHAT THEY 'LL
GET. OK.
ANOTHER POTENTIAL DOWNSIDE OF PURE WATERFALL DEVELOPMENT IS THE LIKELIHOOD
OF THE CLIENT BEING DISSATISFIED WITH THEIR DISTRIBUTED SOFTWARE PRODUCT .
SINCE ALL PRODUCTS ARE DELIVERED BASED ON DOCUMENTED REQUIREMENTS , THE
CUSTOMER MAY NOT KNOW WHAT WILL BE DELIVERED UNTIL IT IS ALMOST COMPLETE .
AT THAT POINT , CHANGES CAN BE DIFFICULT (AND COSTLY ).
* SOME BENIFITS AGILE
! AGILE METHOD
CLIENTS HAVE FREQUENT AND EARLY OPPORTUNITIES TO SEE WORK DELIVERED AND
MAKE DECISIONS AND CHANGES THROUGHOUT A DEVELOPMENT PROJECT .
CUSTOMERS GAIN A STRONG SENSE OF OWNERSHIP BY WORKING EXTENSIVELY AND
DIRECTLY WITH THE PROJECT TEAM THROUGHOUT THE PROJECT .
IF MARKETING TIME FOR A PARTICULAR APPLICATION IS OF GREATER CONCERN THAN
RELEASING THE FULL FEATURE SET ON INITIAL LAUNCH , AGILE CAN QUICKLY GENERATE
A BASIC WORKING SOFTWARE VERSION THAT CAN BE BUILD ON SUCCESSIVE ITERATIONS .
DEVELOPMENT IS OFTEN MORE USER -FOCUSED , POSSIBLY THE RESULT OF FREQUENT AND
MORE GUIDANCE FROM THE CUSTOMER .
8 Benefits of Agile
(TRANSPARENT , EARLY AND PREDICTABLE DELIVERY, COST PREDICTIVE AND
SCHEDULING, ALLOW CHANGE , ENTERPRISE VALUE FOCUSED, USER FOCUSED , QUALITY
IMPROVEMENT)
FROM 8 Benefits of Agile
THE CHANGE FROM WATERFALL METHOD TO AGILE METHOD IS COMPLETELY
REASONABLE WITH CASE STUDY GIVEN .
EG:
- SAVE TIME AND MONEY FOR BANKS AND CUSTOMERS WHEN MAKING TRANSACTIONS .
-THIS PROJECT AND IT'S IMPORTANT TO COMPLETE IT ON TIME AND ON BUDGET .....
Q2:
SOME THINGS WILL HAVE TO CHANGE ON HOW THIS TEAM OPERATES AND HOW KEY
STAKEHOLDERS INTERACT OR ENGAGE ON THIS PROJECT .
The very high degree of customer involvement, while great for the project, may
present problems for some customers who simply may not have the time or interest for this
type of participation.
Agile works best if and only when the development team members are completely
committed to the project.
Because Agile focuses on time-boxed delivery and frequent reprioritization, it’s
possible that some items set for delivery will not be completed within the allotted
timeframe. Additional sprints (beyond those initially planned) may be needed, adding to
the project cost. In addition, customer involvement often leads to additional features
requested throughout the project. Again, this can add to the overall time and cost of the
implementation.
The close working relationships in an Agile project are easiest to manage when the
team members are located in the same physical space, which is not always possible.
However, there are a variety of ways to handle this issue, such as webcams, collaboration
tools, etc.
The iterative nature of Agile development may lead to a frequent refactoring if the full
scope of the system is not considered in the intial architecture and design. Without this
refactoring, the system can suffer from a reduction in overall quality. This becomes more
pronounced in larger-scale implementations, or with systems that include a high level of
integration.
Team members have some web development experience but no mobile development
experience. No one on the team has performance testing experience or User experience
expertise. Also, since this is the team's first quick project, they are not familiar with
technical practices like automated testing, continuous integration, etc.
FROM THE ABOVE , WHAT WILL HAVE TO BE CHANGED ABOUT HOW THIS GROUP WORKS
AND HOW KEY STAKEHOLDERS INTERACT OR PARTICIPATE IN THIS PROJECT AND NEED
HELP AS OUTLINED ABOVE .
Q3: THERE ARE SOME PROJECT CONSTRAINTS LAID OUT IN THE CASE STUDY THAT NEED TO
BE CHANGED /MANAGED SINCE YOU WILL BE USING AGILE AND , IN AGILE , PLANNING ,
ESTIMATION AND TRACKING.
Green Bank wants to attract new customers by capturing remote deposits and
avoiding losing existing customers, so quality and customer service are key.
--> Because all green banking utilities are related to software and hardware, the response time
and finished product will increase accordingly.
Initial estimates suggest the project will take 6 months to complete and
cost about 500,000 USD. Annual operating costs will be approximately $ 150,000 per year
for three years.
Estimated benefit is about $ 400,000 per year for three years.
--> Operating costs will increase proportionally with the number of users but also means the
revenue will increase.
TEAM MEMBERS HAVE SOME WEB DEVELOPMENT EXPERIENCE BUT NO MOBILE
DEVELOPMENT EXPERIENCE . NO ONE ON THE TEAM HAS PERFORMANCE TESTING
EXPERIENCE OR USER EXPERIENCE EXPERTISE . ALSO , SINCE THIS IS THE TEAM 'S
FIRST QUICK PROJECT , THEY ARE NOT FAMILIAR WITH TECHNICAL PRACTICES LIKE
AUTOMATED TESTING , CONTINUOUS INTEGRATION , ETC.
--> MEMBERS NEED A CERTAIN AMOUNT OF TRAINING TO HAVE A FIRM KNOWLEDGE OF
AUTOMATED TESTING , CONTINUOUS INTEGRATION AS WELL AS MOBILE DEVELOPMENT ,
WHICH WILL TAKE LONGER . B UT THIS WILL ALSO ENSURE THAT THE MEMBERS ARE
COMMITTED TO THE PROJECT .
