ba.adityadash@gmail.com Career Highlights: 7+ Experience as a Business Analyst with following skill sets: Certifed Scrum roduct !wner "CS!# $asters in Business Administration "%& and $arketing# Bachelor of Engineering "Computer Science and Engineering# rofcient in writing user stories and acceptance criteria Creating and managing 'acklog "also in(ol(ed in managing sprint and release 'acklogs# Expertise of 'usiness analysis using Agile methodologies )e*uirements gathering from stakeholders and software specifcation management Experience in product re*uirements management and framing short term product road maps Chief liaison 'etween de(elopment+ *uality teams and other pro,ect stakeholders &ranslate 'usiness complex work -ows into e.cient and *uality documentation and specifcations for implementation Analysis of re*uirements+ administering /A0 sessions and managing customer expectations )e*uirement tracing+ gap analysis+ user acceptance testing and product management Career Obecti!e &o excel as a senior analyst within a dynamic company and le(erage my extensi(e technical skills and 'usiness experience to produce top results generating signifcant satisfaction for me and the company "ech#ical "ools: $eb based tech#ologies: 1&$2+ /a(aScript+ 3B Script+ CSS+ 4$2 %ra&hics'(ser )#ter*ace Desig#ers: hotoshop+ %llustrator+ Balsami* $ockups $or+ ,o- .a#ageme#t: $S 3isio and )ational )ose /e01ireme#t ma#ageme#t tools: &eam 5oundation Ser(er "&5S#+ Scrum6orks+ Entire $icrosoft o.ce suite with extensi(e usage of 6ord+ & and mainly Excel7 De*ect .a#ageme#t tools: Bug8illa and &5S E/2: Basic 9nowledge a'out SA ):;7 6orked on a pro,ect "Business rocess %ntegration using SA ):; "5%:$$:S0## during academics7 Ed1catio# Details a7 $asters of Business Administration in Ad(anced %nformation &echnology '7 Bachelor of Engineering in Computer Science 2roect History 3i*e Care Ce#ters o* America Jan 2014 to Present .ea#i#g*1l (se 4tage 5 6.(57 certi8catio# *or Eligible 2ro*essio#als Designation: Senior Business Analyst &he C$S Stage < 5inal )ule from <=>< specifes the criteria that eligi'le professionals+ eligi'le hospitals+ and critical access hospitals "CA1s# must meet in order to participate in Stage < of the $edicare and $edicaid E1) %ncenti(e rograms7 Stage < uses a core and menu structure for o',ecti(es that pro(iders must achie(e in order to demonstrate meaningful use7 Core o',ecti(es are o',ecti(es that all pro(iders must meet7 Roles and Responsibilities: Created use cases of existing processes in di?erent 'usiness areas in consultation with the 'usiness stake holder 6orked as the 'ackup Scrum master in a'sence of the Scrum master and maintained steady (elocity of the sprints7 2ead and managed Scrum meeting discussing a'out impediments and keeping a close track a'out pro,ect@s progress articipated and contri'uted into Sprint planning and si8ing:estimation of 'usiness features with entire team along with the scrum master 0e(eloped clear and concise re*uirements "user stories+ work-ows+ diagrams# and documentation of prioriti8ed functional re*uirements that can 'e con(erted to test plans 2ead the team of ; 'usiness analyst and 5inali8ed functional re*uirements through /A0 sessions with 'usiness users7 Contri'uted acti(ely with the &ech team to come up with accurate and e.cient system design "architecture and A%# 6orked closely with ro,ect $anagers erformed resource planning:le(eling to meet the pro,ect needs7 &racked and prioriti8ed defects and assigned to de(elopment teams during the BA and AA& testing cycle7 6orked closely with Business team to manage customer expectations 'y planning and forecasting deli(era'les7 E(aluated scope change re*uest and prioriti8ed them to meet the schedules and deli(era'les7 %nter(iewed potential resources and helped organi8ation in getting new 'usiness analysts on 'oard Consulted in adopting Agile practices and helped the pro,ect team impro(e 'urn downs and 'rought steady (elocity across multiple sprints 2ead and Super(ised BA team to ensure less defect leakages with high test scenario co(erage of pro,ect features7 Esta'lished and maintained clear scope 'oundaries for the solution7 )e(iewed &est scenarios of BA team and ensured >==C test scenario co(erage 2ead AA& on the sprint deli(era'les e-.Ds9 )#c. Feb 2013 to Jan 2014 :illi#g 4ystem i#tegratio# -ith EH/ a#d Claims .a#ageme#t Business Analyst A Billing system was 'uilt+ with its roots originating from an E1)7 &his pro,ect 'egan with the o',ecti(e of 'uilding features re*uired 'y an E1) to 'e integrated with a Billing System7 2ater+ a fully functional 'illing management system was 'uilt7 &he 'illing system was capa'le of generating in(oices out of the super 'ill section of a clinical (isit "eligi'ility (erifcation <7=:<7>#7 %n(oices were then created with implementation of complex 'usiness rules and few of them were automated7 %n(oices were then cleaned with accurate and correct data to 'e con(erted into claims7 &he claims were then generated "D;7 and C$S >E==# 'ased on numerous factors7 &hese claims were then electronically transmitted through clearing houses7 !nce the payment is recei(ed from payers "D;E#+ these payments were posted to in(oices7 )eporting was also an important part of this pro,ect where in patient due reminders were electronically generated and transmitted through a custom 'uilt patient portal7 Roles and Responsibilities: 2ead and managed Scrum meeting discussing a'out impediments and keeping a close track a'out pro,ect@s progress articipated and contri'uted into Sprint planning and si8ing:estimation of 'usiness features with entire team along with the scrum master 0e(eloped clear and concise re*uirements "user stories+ work-ows+ diagrams# and documentation of prioriti8ed functional re*uirements that can 'e con(erted to test plans 2ead the team of F 'usiness analyst Critically e(aluated information gathered from multiple sources+ reconciled con-icts+ decomposed highGle(el information into details+ a'stract up from lowGle(el information to a general understanding+ and distinguished user re*uests from the underlying true needs7 Articulated the implications of implementing new technologies in the current 'usiness and technology framework7 Colla'orated with de(elopers and su',ect matter experts to esta'lish the technical (ision and analy8e tradeo?s 'etween usa'ility and performance needs7 0e(eloped clear and concise re*uirements "user stories+ work-ows+ diagrams# and documentation of prioriti8ed functional re*uirements that can 'e con(erted to test plans+ use cases+ and system conceptual designs to meet performance targets and de(elopment pro,ect plans %dentifed and reported change control product features under the guidance of the program manager and the product teams7 Colla'orated with pro,ect management entities to create and manage realistic timelines and identify:mitigate risks and dependencies7 Conducted 5unctional &esting H defect analysis7 Clarifed defect implications and suggestions according to priority "%mpact Analysis# e-.Ds9 )#c .ea#i#g*1l (se 4tage 1 6.(7 Certi8catio# a#d Electro#ic /e&orti#g o* C;.s Noe!ber 2012 " Feb 2013 $eaningful Ase is the phrase used in the American )eco(ery and )ein(estment Act of <==I to descri'e the 5ederal Jo(ernment@s goals for how E1) technology is implemented and used 'y either hospitals or am'ulatory clinics "doctor@s o.ces#7 &he Centers for $edicare and $edicaid Ser(ices "C$S# pro(ides incenti(e payments to eligi'le professionals and hospitals for adopting and implementing procedures that demonstrate they use a certifed E$) in conformance with these goals7 &here are reim'ursement programs run under 'oth the $edicare "federal# system and $edicaid "each state# systems7 &he $edicare program was the primary focus of the pro,ect at this time7 Roles and Responsibilities: Elicitation G 0isco(ered the underlying 'usiness need to 'e addressed and information related to the product and pro,ect re*uirements+ often through con(ersations with stakeholders7 Analy8ing )e*uirements K !rgani8ed specifed and modeled the re*uirements to ensure they are complete and unam'iguous7 Specifying )e*uirements K 0ocumented the re*uirements in a format that can 'e shared with stakeholders7 3alidating and 3erifying )e*uirements K Ensured the re*uirements map to the real 'usiness need+ are appro(ed 'y all rele(ant stakeholders+ and meet essential *uality standards7 erformed research to assist in the de(elopment of pro,ect scope+ defne re*uirements and propose changes Collected data+ analy8ed trends and collected reports as re*uested 'y 'usiness team and test proctor 6ork proacti(ely with Scrum master and the team in o(ercoming daily impediments identifed during daily scrum standup 6orked closely with 0rummond test proctor and ensured proper and e?ecti(e 'usiness process 'eing scoped in the re*uirements as well as ensure its implementation Cli#ical Decisio# 4ystem < C1stom Cli#ical /1les E#gi#e August 2011 " Noe!ber 2012 &he Clinical rules K C0S system is used as a guidance tool for a clinical user or pro(ider:physicians+ so that they can 'e informed a'out certain predefned process which a patient needs to followL 'ased on his:her demographics+ medications+ diagnosis+ and other health related attri'utes7 A user can create complex clinical rules using this C0S system 'y using an interacti(e Criteria Editor for fltering patients+ defning clinical actions which needs to 'e performed on patients+ automate process of check and check out process formalities for a patient+ allow scheduling of appointments with a healthcare pro(ider+ prescri'e rele(ant medications 'ased on patient@s health history and current pro'lems+ and many more clinical functions7 &he system also allows managing di?erent categories of healthcare practices for disease management+ pre(enti(e care and immuni8ations7 Roles and Responsibilities: Created use cases of existing processes in di?erent 'usiness areas 5inali8ed functional re*uirements through /A0 sessions with 'usiness users7 Contri'uted acti(ely with de(elopment team on the technical design to meet functional criteria7 erformed resource planning:le(eling to meet the pro,ect needs7 &racked and prioriti8ed defects and assigned to de(elopment teams during the BA and AA& testing cycle7 E(aluated scope change re*uest and prioriti8ed them to meet the schedules and deli(era'les7 Asing multiple elicitation techni*ues+ conducted sessions with customers to defne detailed 'usiness re*uirements for solution de(elopment7 Esta'lished and maintained clear scope 'oundaries for the solution7 Colla'orated with de(elopers and su',ect matter experts to esta'lish the technical (ision and analy8e tradeo?s 'etween usa'ility and performance needs7 0e(eloped clear and concise re*uirements "user stories+ work-ows+ diagrams# and documentation of prioriti8ed functional re*uirements that can 'e con(erted to test plans+ use cases+ and system conceptual designs to meet performance targets and de(elopment pro,ect plans %dentifed and reported change control product features under the guidance of the program manager and the product teams7 2atie#t 2ortal Feb 2011 " August 2011 atient portal is an interface that allows patients to access patient information online7 %t ena'les 'oth ro(iders and patients to manage patient data e.ciently7 atient portal pro(ides the patient with the a'ility to (iew his health information+ (iew his test results+ and communicate with the pro(ider and schedule appointments7 &he atient ortal is a we'G'ased system that ser(es as a secure communication link 'etween patients and the clinic7 6hen a patient logs in to the ortal with user name and password+ they can see information that is pulled from their electronic record at the clinic and displayed on the we' page7 Roles and Responsibilities: Created use cases of existing processes in di?erent 'usiness areas 5inali8ed functional re*uirements through /A0 sessions with 'usiness users7 Contri'uted acti(ely with de(elopment team on the technical design to meet functional criteria7 erformed resource planning:le(eling to meet the pro,ect needs7 &racked and prioriti8ed defects and assigned to de(elopment teams during the BA and AA& testing cycle7 E(aluated scope change re*uest and prioriti8ed them to meet the schedules and deli(era'les7 Asing multiple elicitation techni*ues+ conducted sessions with customers to defne detailed 'usiness re*uirements for solution de(elopment7 Esta'lished and maintained clear scope 'oundaries for the solution7 Colla'orated with de(elopers and su',ect matter experts to esta'lish the technical (ision and analy8e tradeo?s 'etween usa'ility and performance needs7 %dentifed and reported change control product features under the guidance of the program manager and the product teams7 =odlee9 )#c. Feb 2010 " Feb 2011 Business Analyst $oneyCenter is a 5$ application used widely 'y around 7= $illion users worldwide7 %t pro(ides a snapshot of your spending in multiple accounts and helps users disco(er uni*ue facts a'out their spending nature and spending pattern7 Mot only it pro(ides insights into your expenses+ it also allows you to add multiple accounts "'ank accounts+ loans+ tele(ision+ cell phone+ etc# in one place and generate cash -ows for multiple accounts7 Roles and Responsibilities: Created use cases of existing processes in di?erent 'usiness areas erformed resource planning:le(eling to meet the pro,ect needs7 &racked and prioriti8ed defects and assigned to de(elopment teams during the BA and AA& testing cycle7 E(aluated scope change re*uest and prioriti8ed them to meet the schedules and deli(era'les7 )esponsi'le for complete re*uirements elicitation and management in the pro,ect in an Agile de(elopment en(ironment Asing multiple elicitation techni*ues+ conducted sessions with customers to defne detailed 'usiness re*uirements for solution de(elopment7 0e(eloped clear and concise re*uirements "user stories+ work-ows+ diagrams# and documentation of prioriti8ed functional re*uirements that can 'e con(erted to test plans+ use cases+ and system conceptual designs to meet performance targets and de(elopment pro,ect plans7 %dentifed and reported change control product features under the guidance of the program manager and the product teams7 /E4" A2) )m&leme#tatio# o* =odlee 4D>s August 200# " Feb 2010 Asso$iate Business Analyst Nodlee S09 de(elopment was 'ased on the concept of )epresentational state transfer ")ES&# proxy architecture7 )ES&Gstyle architectures consist of clients and ser(ers7 Clients initiate re*uests to ser(ersL ser(ers process re*uests and return appropriate responses7 )e*uests and responses are 'uilt around the transfer of representations of resources7 &he client 'egins sending re*uests when it is ready to make the transition to a new state7 6hile one or more re*uests are outstanding+ the client is considered to 'e in transition7 &he representation of each application state contains links that may 'e used next time the client chooses to initiate a new state transition7 &he name O)epresentational State &ransferO is intended to e(oke an image of how a wellGdesigned 6e' application 'eha(es: a network of we' pages "a (irtual stateGmachine#+ where the user progresses through the application 'y selecting links "state transitions#+ resulting in the next page "representing the next state of the application# 'eing transferred to the user and rendered for their use7 Nodlee S09 documentation empowered de(elopers all across the glo'e to refer to the S09 documents and 'uild small fnancial applications "5inApps# to 'e hosted inside company@s proprietary product P$oneyCenterQ7 &he S09 used fnancial data of a user@s linked accounts residing in a data'ase and render small useful applications7 Roles and Responsibilities: Created uses cases of existing processes in di?erent 'usiness areas 5inali8ed functional re*uirements through /A0 sessions with 'usiness users7 Contri'uted acti(ely with de(elopment team on the technical design to meet functional criteria7 erformed resource planning:le(eling to meet the pro,ect needs7 &racked and prioriti8ed defects and assigned to de(elopment teams during the BA and AA& testing cycle7 E(aluated scope change re*uest and prioriti8ed them to meet the schedules and deli(era'les7 )esponsi'le for complete re*uirements elicitation and management in the pro,ect in an agile de(elopment en(ironment Asing multiple elicitation techni*ues+ conducted sessions with customers to defne detailed 'usiness re*uirements for solution de(elopment7 Esta'lished and maintained clear scope 'oundaries for the solution7 Colla'orated with de(elopers and su',ect matter experts to esta'lish the technical (ision and analy8e tradeo?s 'etween usa'ility and performance needs7 0e(eloped clear and concise re*uirements "user stories+ work-ows+ diagrams# and documentation of prioriti8ed functional re*uirements that can 'e con(erted to test plans+ use cases+ and system conceptual designs to meet performance targets and de(elopment pro,ect plans Ser(ed as the conduit 'etween the customer community "internal and external customers# and the software de(elopment team through which re*uirements -ow7 %dentifed and reported change control product features under the guidance of the program manager and the product teams7 Credere )#*otech r1?i# < /1ral ?i#a#ce .a#ageme#t .od1le January 200# " August 200# Senior Business Analyst ru5in is a )ural 5inance $anagement System7 &his application stored data a'out di?erent fnancing schemes like $icro Credit+ 1ousing programs+ %nsurance+ Sa(ings+ )emittance+ etc7 &here was a separate module for storing the documents in /EJ format along with classifcation of documents7 Roles and Responsibilities: Created uses cases of existing processes in di?erent 'usiness areas 5inali8ed functional re*uirements through /A0 sessions with 'usiness users7 Contri'uted acti(ely with de(elopment team on the technical design to meet functional criteria7 erformed resource planning:le(eling to meet the pro,ect needs7 &racked and prioriti8ed defects and assigned to de(elopment teams during the BA and AA& testing cycle7 E(aluated scope change re*uest and prioriti8ed them to meet the schedules and deli(era'les7 )esponsi'le for complete re*uirements elicitation and management in the pro,ect in an agile de(elopment en(ironment Asing multiple elicitation techni*ues+ conducted sessions with customers to defne detailed 'usiness re*uirements for solution de(elopment7 Esta'lished and maintained clear scope 'oundaries for the solution7 Colla'orated with de(elopers and su',ect matter experts to esta'lish the technical (ision and analy8e tradeo?s 'etween usa'ility and performance needs7 0e(eloped clear and concise re*uirements "user stories+ work-ows+ diagrams# and documentation of prioriti8ed functional re*uirements that can 'e con(erted to test plans+ use cases+ and system conceptual designs to meet performance targets and de(elopment pro,ect plans Ser(ed as the conduit 'etween the customer community "internal and external customers# and the software de(elopment team through which re*uirements -ow7 %dentifed and reported change control product features under the guidance of the program manager and the product teams7 i@?1#ds <)#!estme#t .a#ageme#t 4ol1tio# January 200% " De$e!ber 200& Business Analyst iR5unds is an %n(estment management and ortfolio analysis software 'eing used 'y in(estment 'anks and MB5%s to store the details of their client@s in(estment and carry out analysis on the same7 &he system stores details a'out di?erent trades for a particular entity "the client# and generates automated reports a'out the portfolios7 Roles and Responsibilities: Created uses cases of existing processes in di?erent 'usiness areas 5inali8ed functional re*uirements through /A0 sessions with 'usiness users7 Contri'uted acti(ely with de(elopment team on the technical design to meet functional criteria7 erformed resource planning:le(eling to meet the pro,ect needs7 &racked and prioriti8ed defects and assigned to de(elopment teams during the BA and AA& testing cycle7 E(aluated scope change re*uest and prioriti8ed them to meet the schedules and deli(era'les7 )esponsi'le for complete re*uirements elicitation and management in the pro,ect in an agile de(elopment en(ironment Asing multiple elicitation techni*ues+ conducted sessions with customers to defne detailed 'usiness re*uirements for solution de(elopment7 Esta'lished and maintained clear scope 'oundaries for the solution7 Colla'orated with de(elopers and su',ect matter experts to esta'lish the technical (ision and analy8e tradeo?s 'etween usa'ility and performance needs7 0e(eloped clear and concise re*uirements "user stories+ work-ows+ diagrams# and documentation of prioriti8ed functional re*uirements that can 'e con(erted to test plans+ use cases+ and system conceptual designs to meet performance targets and de(elopment pro,ect plans Ser(ed as the conduit 'etween the customer community "internal and external customers# and the software de(elopment team through which re*uirements -ow7 %dentifed and reported change control product features under the guidance of the program manager and the product teams7 Certi8catio#s Certifed Scrum roduct !wner "CS!# from ScrumAlliance Certifcate in Metworking in 2inux En(ironment from 4%$B+ Bhu'aneswar