$$$$
{{ $t($store.state.user.experience_value_in_dollars) }}
Expert
{{ $t($store.state.user.experience_search_name) }}
0
jobs
Scrum Master & Jira Administrator with 18 years experience working on IT Projects
Bobby Rai
,
Maidstone, United Kingdom
Experience
Other titles
Skills
I'm offering
Certified Scrum Master (CSM) with 18 years of experience working on IT projects within retail, energy, automotive, digital media and finance sectors. Worked daily on agile projects for the last 10 years, initiating/utilising the use of both Scrum and Kanban frameworks. Coached & mentored individuals, teams and organisations to continuously improve their processes and output.
Markets
United States
(Remote
only)
United Kingdom
France
(Remote
only)
Germany
(Remote
only)
Lithuania
(Remote
only)
Denmark
(Remote
only)
Norway
(Remote
only)
Sweden
(Remote
only)
Finland
(Remote
only)
Links for more
Once you have created a company account and a job, you can access the profiles links.
Language
English
Fluently
Ready for
Larger project
Ongoing relation / part-time
Full time contractor
Available
My experience
1998 - ?
freelance
Overview of Skills
Multiple Projects.
Agile Framework Adoption:
● Played a pivotal role in introducing agile ceremonies into the scrum teams, helping the team to understand the expected outcomes from the ceremonies
● Introduced/oversaw the creation of user stories to capture acceptance criteria, and ensured a standardised format was agreed and used for titles and sub-items
● Introduced the 'scrum of scrums' concept - ensured core members of each scrum team met on a consistent basis to highlight and discuss dependencies
● Introduced Scrum@Scale concepts to senior stakeholders, with a view to implementing the framework across various departments within EDF Energy
Stakeholder Engagement:
● Encouraged stakeholder engagement by sharing Jira boards, ensuring scrum team progress could be ascertained by stakeholders whenever desired.
● Invited stakeholders to daily scrums to help them understand our adoption of the scrum framework.
● Created 'information radiators'/dashboards (including burn up charts & blockers) for stakeholders to track progress
Product Owner Engagement:
● Ensured potential non-functional requirements were considered by the product owner and discussed with clients, and ensured requirements were added into the product backlog
● Ensured release related stories/tasks were added to the backlog in order to eradicate 'hidden effort' that was associated when releasing into production environments (i.e. creation of release notes, rollback plans etc.)
● Helped product owners rank user stories in priority order that were both functional and non-functional, which helped to highlight both dependencies and additional stories for the backlog
● Ensured the backlog was maintained by the product owner and contained enough detail within user stories earmarked for the next sprint
● Introduced a standardised BDD format for user stories and acceptance criteria to help Product Owners structure content
● Introduced a roadmap containing epics, divided into quarter year deliverables, which helped to improve budgeting & resourcing
● Highlighted the importance of including maintenance tasks into each sprint which reduced the amount of technical debt
Jira Global & Project Administration:
● Jira Project administrator with responsibilities to implement workflows, transitions and statuses to ensure robustness and clarity existed for processes associated with both task and change management
● Gathered user requirements and recommended/implemented solutions based upon 18 years of experience working within IT projects
● Analysed various 3rd Party add-ons to introduce functionality that wasn't available within the Jira Core offering and selected the most suitable options based upon both functionality and cost efficiency
● Identified solutions that were specific to desired working practises, such as email triggering & template design, conditional validation and digital signatures
● Implemented custom fields & screens, tailored to specific working practises of various teams and ensuring no conflicts arose with setup/configurations
● Created Dashboards to help visuals and prioritise workloads
● Devised various reports using JQL that aided month-end reconciliation and the scheduling of forthcoming work
● Worked with Infrastructure teams to drive through active directory integration and SSO
● Trained over 90 users on how to use Jira and introduced them to the implemented processes via roleplay
Team Engagement & Coaching:
● Presented the concept of 'vertically sliced' user stories to the scrum teams, ensuring any problems with integration points were highlighted much earlier than 'horizontally sliced' (i.e. mini waterfall) stories
● Introduced Kanban style WIP limits to team members personal workloads to reduce context switching and inefficiency
● Helped the teams create and commit to a definition of done, and held mid-sprint reviews to discuss/gain insight into whether the goals would be met by the end of the sprint
● Helped the teams to engender collective responsibility to ensure the definition of done was met for each story
● Removed and helped to progress blockers experienced by team members
● Encouraged team members to identify stories that were suitable for paired programming
● Spent time with new team members to provide an insight into how Scrum & Kanban frameworks were being implemented
● Organised team lunches to welcome new starters and after work drinks to celebrate key milestones
● Organised and facilitated lean beer/coffee meetings, ensuring that not only action points were captured and acted upon, but team members had an opportunity to bond within a jovial atmosphere
Sprint Pre-Planning/Refinement:
● Instigated '3 Amigo' / Epic Refinement Sessions, whereby product owners, developers and QAs collaborated to present and enhance/refine/amend user stories and break down stories into sub-tasks
● Provided a checklist to 3 Amigo participants to ensure discussions occurred to identify dependencies and potential impediments to story completion
● Introduced a definition of ready for each user story and encouraged the scrum teams to 'push back' should the definition not be met
● Setup and facilitated backlog refinement sessions for teams to see forthcoming stories earmarked for the next sprint/clarify areas of ambiguity with either the product owner or fellow team members
Estimations:
● Ensured user stories contained story point estimations, added during 3 Amigo and/or refinement Sessions
● Ensured spikes were timeboxed and inspected whether timeboxes were being adhered to
● Introduced T-shirt sizing to a Kanban team which helped the product owner with forecasting
Sprint (and Capacity) Planning:
● Helped teams to formulate a sprint goal for every sprint
● Helped teams to ensure that the amount of work they committed to each sprint was estimated not to over burden or under utilise the teams
● Recommended contingency was built into each sprint by ensuring each scrum team was utilised up to a maximum of 80% and took into consideration holidays/time off etc. This ensured 20% capacity could be directed towards technical debt/maintenance tasks, and also act as contingency time for underestimated/previously unknown tasks
● Ensured a sprint backlog was formulated and committed to by the scrum teams within the planning meeting and each user story was understood by the team via thumb voting
● Created a checklist to ensure there was consistency between planning sessions
Daily Scrums:
● Facilitated daily scrum meetings and encouraged follow up discussions at the conclusion of the scrum (and not during the scrum itself)
● Ensured the scrum teams remained focused on the highest priority user stories
● Used traditional '3 question' and sprint board/user story techniques to facilitate the daily scrum
● Setup slack bots to gather responses for the 3 question approach, which ensured the daily scrum focused on high priority issues/blockers
● Coached the scrum team to understand that the scrum is not a status update for the product owner or scrum master, and encouraged members to highlight impediments and risks associated with their tasks.
● Encouraged teams to play rock-paper-scissors before Monday morning scrums to energise and invigorate the team
Sprint Review:
● Facilitated sprint review meetings, ensuring the sprint goal(s) were revisited to ascertain whether the goals had been met
● Ensured new functionality could be demonstrated within the review to stakeholders (test data had been setup, environments were available etc.)
● Ensured user stories that were committed to within sprint planning were inspected in relation to the definition of done
● Assisted the product owner by amending existing requirements or adding new requirements (identified by the clients during the sprint review) into the product backlog
Retrospectives:
● Used a variety of well known agile retrospectives techniques which (such as the starfish retrospective) and questions created by myself based on observations made during the last sprint/cycle
● Adapted retrospectives to ensure they were effective for distributed teams
● Helped to identify and capture action points for aspects deemed to need improvement by the scrum teams and ensured tasks were added to the backlog (where applicable)
● Ensured action points from the previous retrospective were assessed for inclusion into the sprint backlog during sprint planning
Reporting:
● Provided reports extracted from Jira that adhered to Deutsche Bank compliance department templates
● Setup burn down charts to aid monitoring of progress during the sprint
● Tracked actual and estimated story point completion per sprint to help measure velocity
● Produced go live and epic completion forecasts based on team velocity
● Created 'Sprint Summary' reports for internal stakeholders/product owners, which showed completed stories, open defects and reasons behind non-completion of stories
● Reported on cycle & lead times, along with throughput for teams using Kanban
Kanban:
● Moved a team from Scrum to Kanban due to the Kanban approach fitting better with both team release cycles and adherence to client timescales
● Introduced WIP Limits, which saw an improvement in cycle times and increased discipline from the product owner
● Intermingled Scrum and Kanban approaches (Scrumban) by having daily stand ups and retrospectives at regular intervals
● Helped the marketing team to adopt Kanban to help organize and plan their deliverables
Recruitment:
● Interviewed Scrum Master candidates to determine suitability and competence
● As a Test Lead, recruited and lead a multi-skilled testing team covering both manual and automated testing
● Reviewed CVs, shortlisted suitable applicants, conducted interviews and made offers to suitable candidates
● Created scenario based questions and test exercises to be used within interviews
● Used both telephone and video interviews to help hire offshore resources
Lead/Senior Test Skills:
● Managed an onshore/offshore QA team, ensuring tasks were being completed to a high standard in a timely manner
● Acted as the 1st point of contact for offshore resources and ensuring blockages to offshore execution were promptly rectified
● Worked on multi-time zone projects and adapted quickly to the challenges faced working within such environments
● Signed off new functionality/code for deployment into production environments
● Created test coverage/completion reports to measure progress/identify where extra resources were needed
● Demonstrated new functionality to be released and known defects to stakeholders prior to UAT
● Reviewed user stories to ensure information contained within was sufficient enough to include test estimates
● Contributed to and running daily scrums, ensuring any issues/blockages were highlighted & providing information for resolution
● Ensured defects not fixed within the current sprint (i.e. after triage) were backlogged
● Regularly refined the backlog to ensure defects contained within were still relevant
● Created both detailed and high-level test strategy documentation for various projects, including information such as testing scope and objectives, tools to be used, roles and responsibilities & entry/exit criteria etc
● Implemented a Behaviour Driven Development (BDD) approach to test scripting with the intention of harmonising with acceptance criteria and potential automation tools (Cucumber)
● Created regression & smoke test packs, ensuring content was kept valid SSO functionality was released
● Played a pivotal role in introducing agile ceremonies into the scrum teams, helping the team to understand the expected outcomes from the ceremonies
● Introduced/oversaw the creation of user stories to capture acceptance criteria, and ensured a standardised format was agreed and used for titles and sub-items
● Introduced the 'scrum of scrums' concept - ensured core members of each scrum team met on a consistent basis to highlight and discuss dependencies
● Introduced Scrum@Scale concepts to senior stakeholders, with a view to implementing the framework across various departments within EDF Energy
Stakeholder Engagement:
● Encouraged stakeholder engagement by sharing Jira boards, ensuring scrum team progress could be ascertained by stakeholders whenever desired.
● Invited stakeholders to daily scrums to help them understand our adoption of the scrum framework.
● Created 'information radiators'/dashboards (including burn up charts & blockers) for stakeholders to track progress
Product Owner Engagement:
● Ensured potential non-functional requirements were considered by the product owner and discussed with clients, and ensured requirements were added into the product backlog
● Ensured release related stories/tasks were added to the backlog in order to eradicate 'hidden effort' that was associated when releasing into production environments (i.e. creation of release notes, rollback plans etc.)
● Helped product owners rank user stories in priority order that were both functional and non-functional, which helped to highlight both dependencies and additional stories for the backlog
● Ensured the backlog was maintained by the product owner and contained enough detail within user stories earmarked for the next sprint
● Introduced a standardised BDD format for user stories and acceptance criteria to help Product Owners structure content
● Introduced a roadmap containing epics, divided into quarter year deliverables, which helped to improve budgeting & resourcing
● Highlighted the importance of including maintenance tasks into each sprint which reduced the amount of technical debt
Jira Global & Project Administration:
● Jira Project administrator with responsibilities to implement workflows, transitions and statuses to ensure robustness and clarity existed for processes associated with both task and change management
● Gathered user requirements and recommended/implemented solutions based upon 18 years of experience working within IT projects
● Analysed various 3rd Party add-ons to introduce functionality that wasn't available within the Jira Core offering and selected the most suitable options based upon both functionality and cost efficiency
● Identified solutions that were specific to desired working practises, such as email triggering & template design, conditional validation and digital signatures
● Implemented custom fields & screens, tailored to specific working practises of various teams and ensuring no conflicts arose with setup/configurations
● Created Dashboards to help visuals and prioritise workloads
● Devised various reports using JQL that aided month-end reconciliation and the scheduling of forthcoming work
● Worked with Infrastructure teams to drive through active directory integration and SSO
● Trained over 90 users on how to use Jira and introduced them to the implemented processes via roleplay
Team Engagement & Coaching:
● Presented the concept of 'vertically sliced' user stories to the scrum teams, ensuring any problems with integration points were highlighted much earlier than 'horizontally sliced' (i.e. mini waterfall) stories
● Introduced Kanban style WIP limits to team members personal workloads to reduce context switching and inefficiency
● Helped the teams create and commit to a definition of done, and held mid-sprint reviews to discuss/gain insight into whether the goals would be met by the end of the sprint
● Helped the teams to engender collective responsibility to ensure the definition of done was met for each story
● Removed and helped to progress blockers experienced by team members
● Encouraged team members to identify stories that were suitable for paired programming
● Spent time with new team members to provide an insight into how Scrum & Kanban frameworks were being implemented
● Organised team lunches to welcome new starters and after work drinks to celebrate key milestones
● Organised and facilitated lean beer/coffee meetings, ensuring that not only action points were captured and acted upon, but team members had an opportunity to bond within a jovial atmosphere
Sprint Pre-Planning/Refinement:
● Instigated '3 Amigo' / Epic Refinement Sessions, whereby product owners, developers and QAs collaborated to present and enhance/refine/amend user stories and break down stories into sub-tasks
● Provided a checklist to 3 Amigo participants to ensure discussions occurred to identify dependencies and potential impediments to story completion
● Introduced a definition of ready for each user story and encouraged the scrum teams to 'push back' should the definition not be met
● Setup and facilitated backlog refinement sessions for teams to see forthcoming stories earmarked for the next sprint/clarify areas of ambiguity with either the product owner or fellow team members
Estimations:
● Ensured user stories contained story point estimations, added during 3 Amigo and/or refinement Sessions
● Ensured spikes were timeboxed and inspected whether timeboxes were being adhered to
● Introduced T-shirt sizing to a Kanban team which helped the product owner with forecasting
Sprint (and Capacity) Planning:
● Helped teams to formulate a sprint goal for every sprint
● Helped teams to ensure that the amount of work they committed to each sprint was estimated not to over burden or under utilise the teams
● Recommended contingency was built into each sprint by ensuring each scrum team was utilised up to a maximum of 80% and took into consideration holidays/time off etc. This ensured 20% capacity could be directed towards technical debt/maintenance tasks, and also act as contingency time for underestimated/previously unknown tasks
● Ensured a sprint backlog was formulated and committed to by the scrum teams within the planning meeting and each user story was understood by the team via thumb voting
● Created a checklist to ensure there was consistency between planning sessions
Daily Scrums:
● Facilitated daily scrum meetings and encouraged follow up discussions at the conclusion of the scrum (and not during the scrum itself)
● Ensured the scrum teams remained focused on the highest priority user stories
● Used traditional '3 question' and sprint board/user story techniques to facilitate the daily scrum
● Setup slack bots to gather responses for the 3 question approach, which ensured the daily scrum focused on high priority issues/blockers
● Coached the scrum team to understand that the scrum is not a status update for the product owner or scrum master, and encouraged members to highlight impediments and risks associated with their tasks.
● Encouraged teams to play rock-paper-scissors before Monday morning scrums to energise and invigorate the team
Sprint Review:
● Facilitated sprint review meetings, ensuring the sprint goal(s) were revisited to ascertain whether the goals had been met
● Ensured new functionality could be demonstrated within the review to stakeholders (test data had been setup, environments were available etc.)
● Ensured user stories that were committed to within sprint planning were inspected in relation to the definition of done
● Assisted the product owner by amending existing requirements or adding new requirements (identified by the clients during the sprint review) into the product backlog
Retrospectives:
● Used a variety of well known agile retrospectives techniques which (such as the starfish retrospective) and questions created by myself based on observations made during the last sprint/cycle
● Adapted retrospectives to ensure they were effective for distributed teams
● Helped to identify and capture action points for aspects deemed to need improvement by the scrum teams and ensured tasks were added to the backlog (where applicable)
● Ensured action points from the previous retrospective were assessed for inclusion into the sprint backlog during sprint planning
Reporting:
● Provided reports extracted from Jira that adhered to Deutsche Bank compliance department templates
● Setup burn down charts to aid monitoring of progress during the sprint
● Tracked actual and estimated story point completion per sprint to help measure velocity
● Produced go live and epic completion forecasts based on team velocity
● Created 'Sprint Summary' reports for internal stakeholders/product owners, which showed completed stories, open defects and reasons behind non-completion of stories
● Reported on cycle & lead times, along with throughput for teams using Kanban
Kanban:
● Moved a team from Scrum to Kanban due to the Kanban approach fitting better with both team release cycles and adherence to client timescales
● Introduced WIP Limits, which saw an improvement in cycle times and increased discipline from the product owner
● Intermingled Scrum and Kanban approaches (Scrumban) by having daily stand ups and retrospectives at regular intervals
● Helped the marketing team to adopt Kanban to help organize and plan their deliverables
Recruitment:
● Interviewed Scrum Master candidates to determine suitability and competence
● As a Test Lead, recruited and lead a multi-skilled testing team covering both manual and automated testing
● Reviewed CVs, shortlisted suitable applicants, conducted interviews and made offers to suitable candidates
● Created scenario based questions and test exercises to be used within interviews
● Used both telephone and video interviews to help hire offshore resources
Lead/Senior Test Skills:
● Managed an onshore/offshore QA team, ensuring tasks were being completed to a high standard in a timely manner
● Acted as the 1st point of contact for offshore resources and ensuring blockages to offshore execution were promptly rectified
● Worked on multi-time zone projects and adapted quickly to the challenges faced working within such environments
● Signed off new functionality/code for deployment into production environments
● Created test coverage/completion reports to measure progress/identify where extra resources were needed
● Demonstrated new functionality to be released and known defects to stakeholders prior to UAT
● Reviewed user stories to ensure information contained within was sufficient enough to include test estimates
● Contributed to and running daily scrums, ensuring any issues/blockages were highlighted & providing information for resolution
● Ensured defects not fixed within the current sprint (i.e. after triage) were backlogged
● Regularly refined the backlog to ensure defects contained within were still relevant
● Created both detailed and high-level test strategy documentation for various projects, including information such as testing scope and objectives, tools to be used, roles and responsibilities & entry/exit criteria etc
● Implemented a Behaviour Driven Development (BDD) approach to test scripting with the intention of harmonising with acceptance criteria and potential automation tools (Cucumber)
● Created regression & smoke test packs, ensuring content was kept valid SSO functionality was released
Monitoring, QA, Content, Compliance, Recruitment, It, Offshore, Infrastructure, BDD, Testing, Test, Development, Detail, Administrator, Planning, Production, Framework, Processes, Agile, Design, Coaching, Administration, Video, Jira, Active Directory, Marketing, Deployment, Automation, Scripting, Lean, Product owner, User stories, Management, Integration, Kanban, Scrum master, Scrum, Change management
2019 - 2020
freelance
Scrum Master
CBRE.
Scrum Master for a team of nine engineers in two time zones that were building a data pipeline for multiple data sources across the EMEA region. Implemented practises to ensure effective functioning of a distributed team that faced the challenge of a six hour time difference. Assisted and facilitated in the day to day running/coaching of the Scrum team.
Tools/Technologies: Jira Cloud (Admin), GraphQL, Elasticsearch, Postgres, Sharepoint, Confluence
Framework: Scrum
Tools/Technologies: Jira Cloud (Admin), GraphQL, Elasticsearch, Postgres, Sharepoint, Confluence
Framework: Scrum
Scrum, Coaching, Jira, Scrum master, SharePoint, Cloud, Elasticsearch, Graphql, Confluence, Postgres, Framework
2018 - 2019
freelance
Agile Consultant & Jira Global/Project Administrator
Chanel.
Implemented the first digital change request process within Chanel using Jira, moving away from a paper based system. Conducted training sessions with users/change implementers to ensure the Jira tool was effectively utilised for the change control process. Liaised with external auditors to walkthough the implemented process to demonstrate progress made against concerns raised within previous audits. Introduced Kanban ways of working for Infrastructure teams as part of a task management initiative, which helped improve lead times.
Tools/Technologies: Jira (Core) Server 7 & 8, Jira Suite Utilities, Notification Assistant for Jira, Electronic Signature for Jira
Framework: Kanban
Tools/Technologies: Jira (Core) Server 7 & 8, Jira Suite Utilities, Notification Assistant for Jira, Electronic Signature for Jira
Framework: Kanban
Jira, Training, Agile, Management, Kanban, Infrastructure, Server, Administrator, Utilities, Framework, Task management
2018 - 2018
freelance
Scrum Master
EDF Energy.
Devised and implemented a new Scrum framework for a distributed team which included training team members & stakeholders that were unfamiliar with agile working practises. Implemented Jira workflows, transitions and statuses to ensure there was visibility and clarity for both current and future work. Helped product owners & analysts build backlogs of work in user story format to ensure a consistent approach was adopted. Project objective was to improve access to customer data/obtain a single view through a new cloud based data warehouse solution.
Tools/Technologies: Talend, Amazon Redshift & S3, Tableau, Jira/Confluence, Skype
Framework: Scrum
Tools/Technologies: Talend, Amazon Redshift & S3, Tableau, Jira/Confluence, Skype
Framework: Scrum
Scrum, Jira, Scrum master, Training, Agile, Data Warehouse, Cloud, Tableau, Confluence, Amazon, Redshift, Framework
2017 - 2018
freelance
Scrum Master
Jaguar & Land Rover (JLR).
Lead 3 cross-functional teams (located across 3 countries) which built widgets across multiple platforms that allowed JLR
customers to book test drives and service their vehicles.
Moved one of the teams from Scrum to Kanban, as it fitted
more naturally to their flow of incoming work.
Tools/Technologies: PHP, Angular, Slack, Amazon EC2 & Docker
Framework: Scrum, Kanban
customers to book test drives and service their vehicles.
Moved one of the teams from Scrum to Kanban, as it fitted
more naturally to their flow of incoming work.
Tools/Technologies: PHP, Angular, Slack, Amazon EC2 & Docker
Framework: Scrum, Kanban
Php, Scrum, Angular, Docker, Scrum master, Kanban, Test, Service, It, Amazon, Framework
2017 - 2017
freelance
Scrum Master
News UK.
Worked on a digital transformation project for The Times
newspaper, consolidating 12 different codebases (web, iOS, Android, Tablet etc) into one using React Native. Assisted in the day to day running/coaching of two agile teams.
Tools/Technologies: React Native, Jira, (Google) G suite,
Slack
Framework: Scrum
newspaper, consolidating 12 different codebases (web, iOS, Android, Tablet etc) into one using React Native. Assisted in the day to day running/coaching of two agile teams.
Tools/Technologies: React Native, Jira, (Google) G suite,
Slack
Framework: Scrum
React, Scrum, Coaching, IOS, Android, Jira, Scrum master, React Native, Digital transformation, Agile, Transformation, Web, Google, Native, Framework
2016 - 2017
freelance
Scrum Master
Deutsche Bank.
Played a pivotal role in implementing the scrum framework within the Wealth Management division that was using a waterfall based approach. Mentored and coached multiple distributed teams, helping them to deliver high quality code into production on a consistent basis and continuously improve.
Tools/Technologies: Java, FIX protocol, FXall, Autobahn FX, Jira, Bitbucket Server, FinIQ, HP ALM, Jenkins, jFrog Artifactory,
Framework: Scrum
Tools/Technologies: Java, FIX protocol, FXall, Autobahn FX, Jira, Bitbucket Server, FinIQ, HP ALM, Jenkins, jFrog Artifactory,
Framework: Scrum
Java, Scrum, Jira, Scrum master, Jenkins, Management, Server, Production, Framework
2015 - 2016
freelance
Scrum Master & Test Consultant/Manager
The App Business.
Initially started as a Test Manager and evolved into a Scrum Master, working on the Sun Mobile and Sun Football apps on iOS/Android devices. Lead scrum ceremonies and refined processes through inspection and adaption.
Delivered app into production on time.
Tools/Technologies: Ruby, Testflight, HockeyApp, Crashlytics, Genymotion, Android Studio, Mobizen, Charles, Xcode, TestRail,
TestPad, Bitbucket, Jira, uTest, AnthillPro, Trello
Framework: Scrum & Kanban
Delivered app into production on time.
Tools/Technologies: Ruby, Testflight, HockeyApp, Crashlytics, Genymotion, Android Studio, Mobizen, Charles, Xcode, TestRail,
TestPad, Bitbucket, Jira, uTest, AnthillPro, Trello
Framework: Scrum & Kanban
Test, Processes, Manager, Framework, Production, App, Test manager, Trello, Apps, Scrum, Kanban, Android studio, Xcode, Scrum master, Jira, Android, IOS
2011 - 2014
freelance
Lead Test Analyst
Sony Computer Entertainment.
(Contract), London
Built and managed a team of 7 testers which delivered new
functionality for a multiple language (playstation.com) website across multiple devices (Android/iOS/Desktop, Smartphones, PS4, PS3). Worked on an Adobe CQ pilot project, assessing
the feasibility of migrating from an in-house CMS to Adobe CQ.
Tested the transition to Adobe CQ via phased releases into
production.
Tools/Technologies: Java, SQL, Oracle SQL Developer,
Mingle, Quality Centre, Jira, Xenu, Web API, HTML, XML,
JavaScript, CSS, Perforce, Webtrends, Adobe CQ,
SiteCatalyst, ClickMap, CMS, Scrum
Framework: Scrum
Built and managed a team of 7 testers which delivered new
functionality for a multiple language (playstation.com) website across multiple devices (Android/iOS/Desktop, Smartphones, PS4, PS3). Worked on an Adobe CQ pilot project, assessing
the feasibility of migrating from an in-house CMS to Adobe CQ.
Tested the transition to Adobe CQ via phased releases into
production.
Tools/Technologies: Java, SQL, Oracle SQL Developer,
Mingle, Quality Centre, Jira, Xenu, Web API, HTML, XML,
JavaScript, CSS, Perforce, Webtrends, Adobe CQ,
SiteCatalyst, ClickMap, CMS, Scrum
Framework: Scrum
XML, Sitecatalyst, Framework, Perforce, Production, Web, Adobe, Analyst, Developer, Oracle sql, Website, Web API, Test, Javascript, CMS, Jira, Oracle, HTML/CSS/Javascript, Android, IOS, Scrum, API, Java, Sql, Html, Css
2008 - 2011
temp
Lead Test Analyst
Tesco.com.
Lead Tester responsible for launching and maintaining
www.tescoentertainment.com (E-commerce) website.
Manually tested payment/refund processing via various
payment methods (credit/debit/gift cards etc.), order fulfilment
statuses and conditional email triggering.
Tools/Technologies: .Net, C#, MSMQ, BizTalk, NUnit,
TeamCity CI, TFS, MS SQL Server, ETL, Stored Procedures,
VersionOne, HTML, JavaScript, CSS, CMS
Framework: Scrum
www.tescoentertainment.com (E-commerce) website.
Manually tested payment/refund processing via various
payment methods (credit/debit/gift cards etc.), order fulfilment
statuses and conditional email triggering.
Tools/Technologies: .Net, C#, MSMQ, BizTalk, NUnit,
TeamCity CI, TFS, MS SQL Server, ETL, Stored Procedures,
VersionOne, HTML, JavaScript, CSS, CMS
Framework: Scrum
Test, Processing, Framework, Server, Teamcity, BizTalk, NUnit, Analyst, TFS, Net, Website, Stored procedures, Javascript, ETL, C, E-commerce, CMS, SQL Server, HTML/CSS/Javascript, Scrum, Sql, Html, Css
2001 - 2008
job
Test Analyst/Senior Test Analyst at various organisations
Bupa, BT, Tiscali, Legal Services Commission, Virgin.
Media, AON Hewitt10+.
Responsibilities included writing and executing test scripts,
raising defects, creating test plans/strategies, organising and running bug triage sessions with developers &managers
Tools/Technologies: VMware, SQL, Siebel, Set Top Boxes, IPTV, Siebel, Unix, Prince, Mediation, Rating & Billing Systems, IBM AS/400, CDRs, Tomcat, IBM OS/390, JCL, TSO, File Aid, QMF
Framework: Waterfall
Responsibilities included writing and executing test scripts,
raising defects, creating test plans/strategies, organising and running bug triage sessions with developers &managers
Tools/Technologies: VMware, SQL, Siebel, Set Top Boxes, IPTV, Siebel, Unix, Prince, Mediation, Rating & Billing Systems, IBM AS/400, CDRs, Tomcat, IBM OS/390, JCL, TSO, File Aid, QMF
Framework: Waterfall
Sql, Writing, VMware, Unix, Test, Tomcat, Analyst, JCL, Framework, IPTV
My education
1996
-
2000
Nottingham Trent University
Bachelors, Business Information Systems
Bachelors, Business Information Systems
Bobby's reviews
Bobby has not received any reviews on Worksome.
Contact Bobby Rai
Worksome removes the expensive intermediaries and gives you direct contact with relevant talent.
Create a login and get the opportunity to write to Bobby directly in Worksome.
are ready to help you
and get specific bids from skilled talent in Denmark