Your SlideShare is downloading. ×
Hw2 gap analysis linked_in mobile app_sunil kumar gunasekaran_12052012.docx
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Saving this for later?

Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime - even offline.

Text the download link to your phone

Standard text messaging rates apply

Hw2 gap analysis linked_in mobile app_sunil kumar gunasekaran_12052012.docx

396
views

Published on


0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
396
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Gap Analysis forLinked In Mobile App Version 1.2 Prepared by Sunil Kumar Gunasekaran 12/5/2012
  • 2. Table of Contents1) Revision History ............................................................................................. 22) Project Background ....................................................................................... 33) AS-IS (Current Business Process) ............................................................... 44) Description of AS-IS Model .......................................................................... 45) TO-BE (Future Business Process) ............................................................... 56) Description of TO-BE Model ........................................................................ 57) GAP ANALYSIS ............................................................................................ 68) Gap Analysis Approval ................................................................................. 7 1
  • 3. 1) Revision HistoryName Date Changes Reason For Changes Versio n Increase readability ofSteve Baker 12/02/2012 Enhancement of As-Is and AS-IS and TO-BE 1.0 To-Be Columns diagrams. More information isSunil Kumar 12/03/2012 Modification of Project added in the section 1.2 Background information 2
  • 4. 2) Project BackgroundLinkedIn Mobile page views have grown more than 400% year-over-year, making it thefastest growing consumer service on LinkedIn. In order to meet our members’ needs weare in process of redesigning the mobile app. This gives a faster, simpler and bettermobile experience to the linked-in members.The previous Mobile Team performed a study on section of Linked-In mobile users andfound that the feature most-loved by them was the search function which looks up thepotential contacts or meeting-attendees on-the-fly.The team also found several features that were rarely, if ever, used. Color themes werethrown out, as well as business card transfer, a feature that sounds cool but was actuallymore trouble to use than simply handing over a normal business card.Also the app is based in Ruby on Rails due to which a server-side process is spawned foreach user and requests are sent to the back-end. These requests are serial and limited innumber, meaning a backlog of requests could mean delays for the end-user.In the client side, the GUI is 90 percent HTML5 and this has resulted in quite a fewproblems for the users and difficulty for the developers to enhance the GUI of the Appand for including the app in various other platforms like Andriod etc.This Gap analysis is initiated to find out the current business process in depth andunderstand the next version of the Linked-In App and bridge the gap between them byenlisting the missing functionalities and change of technology if required keeping the endusers in mind. 3
  • 5. 3) AS – IS (Current Business Process)4) Description of AS-IS ModelAs seen above there is user looking at the GUI and there are 10 icons in the front page ofLinked-In App namely Search Button, Pop Ups, Recommend, Add Contact, Click forUpdates, Business Card, Click for Groups etc. Also the main features like Groups,Update Streams and inbox are in the second page and make it difficult for the user to goto the second page to access the features present there like inbox and Update Stream.For editing the profile including adding new job skill and responsibility or to edit theprofile photo, the users need to use the computer as seen in the picture which is the majordrawback and shows the primitiveness of the App.The server side configuration is Ruby on Rails which has a disadvantage of increasing theresponse time for the user queries. There is no proper back up of data which can result indata loss during emergency situations. Also the GUI is built using HTML5 as the basis 4
  • 6. leaving little room for improvement of the GUI design and making the app work inmultiple platforms.Another main item noticed in the main page of the App is that many not –so-desiredfeatures like Business Card, Pop ups and ads occupy the valuable space and leave theusers to click more pages inside the navigation structure looking for the main featureslike Inbox and Group. 5) TO-BE (Future Business Process)6) Description of TO-BE ModelIn this model the usage of computerfor editing profile and uploading photo is absent andinstead the edit profile feature is put in the front page of the App. The user is happy sincethe four main features namely edit profile, search groups, update stream and Inbox are 5
  • 7. present right in front of him and he can go ahead in choosing the option he desires andcontinuing with them instead of digging through the navigation.The user also notices that the search box is always present on the top which gives himindependence to search for contacts any time. This helps him to connect with his fellowprofessionals whom he meets within seconds or know about his bio data minutes prior tomeeting him in person giving you a clear advantage. The technology is changed to J2EEand the numbers of servers are increased and also back up system is properly in place.Also the servers are upgraded and many in number and the server side platform ischanged to J2EE decreasing the wait time of the user. Proper back up technology isintroduced to secure the data in times of emergency.7) GAP ANALYSIS Feature Priority  The GUI needs to be split into four main sections to enhance the user experience and give fast access to the High four main features of the Linked-In app.  Edit profile option need to be included in the front page allowing the user to edit profile in seconds and apply High for a job or take a photo and update profile photo instead of resorting to the computer as seen in the AS- IS model.  Search box need to be included in all the pages since it is found to be the single most important feature used by High the people and decreases the navigation time required to reach the search box. 6
  • 8.  25 more servers need to be added in the backend and platform needs to be changed from Ruby on Rails to J2EE to give fast response time for the user queries and Medium have multiple channels to receive and process the user queries.  Enhancement of databases required for fast retrieval of Medium data. Low  Need to enhance back up of data and increase security of the information stored in the database.  The business card feature needs to be removed since it is not liked by many users and actually it makes it Low more difficult send business card than to add them into their network or send invitation.  Other pop ups and ads which are displayed in the front screen need to be removed to give space for the main features to be presented elegantly for the user Medium8) Gap Analysis ApprovalThe undersigned acknowledge they have reviewed the Gap Analysis and authorize andfund the Linked-In Mobile App project. Changes to this project charter will becoordinated with and approved by the undersigned or their designated representatives. 7
  • 9. Signature: Date: 12/05/2012Print Name: Lee GordonTitle: Executive SponsorRole:Signature: Date: 12/05/2012Print Name: Steve BakerTitle: Project ManagerRole:Signature: Date: 12/05/2012Print Name: James WestmanTitle: Business AnalystRole:8
  • 10. 9