Back to work after a long rested weekend
Back to work after a long rested weekend
New Batches Starting soon…
Courses @ #RPA-Uipath ( robotic process automation) & #BA (business analyst) for Healthcare and IT.
Case Studies very much met my expectation of providing real-world, practical insight and application to the skills learned throughout the M.S. Business Intelligence program. Moreover, I expected this course to push me beyond my comfort zone for growth. However, I did not realize I would be given the skills to jump into a 10-K to analyze and support through industry data. I thought I would simply be translating from an end user. I now understand how the organizational mission can be leveraged in extending a BI initiative and meeting the needs of the end user.
The Case Studies course positioned my thinking to that of a Business Analyst. I am now able to credibly find and digest industry materials, case studies, and financial reports. I am now able to elicit the appropriate information from these materials to find innovative activations for an organization’s bottom line and appropriate communicate the need and benefit of such an initiative. The course positioned me to think critically and creatively while requiring that a take an interdisciplinary approach to understand business and technical needs while meeting the needs of all stakeholders involved.
I am now very confident in my post-graduate ability to create a boisterous eFolio to demonstrating my ability to leverage business objectives and increase efficiencies. In my capstone research, I have found a plethora of case studies and I can use the skills from this course to find organizations of interest and help devise an innovative solution to showcase. This course also improved my confidence by clarifying the need for cognitive skills in becoming a Business Analyst, I was extremely concerned about my lack of technical skills. However, with my new understanding of case analysis, I feel confident in my ability to leverage my naturally analytical, process oriented, creative mindset to benefit business. I can now go beyond simply offering a solution to a known problem by allowing the end user, the industry, the company, and my creativity inform a novel solution or opportunity. I now have a full scope understanding of the professional range in Big Data and understand how to leverage my current strengths while working toward others needed.
Our client produces applications software that provides information capture, process management, data integration, customer communications management and analytics.
The Business Analyst is a pivotal member of the project team and will work with clients and stakeholders to reach shared understanding of business needs and how these can translate into a value-driven solution.
#businessanalyst #analyst #clientfacing #coordination #requirementgathering #itjobs #tokyo #japan #vision
So many Words, so little sense.
Back in the heady days of SSADM ( anyone remember that? ) and for a short while after, there existed a rare beast known as a Systems Analyst. These were generally intelligent individuals with a degree of common sense and some technical skills, who could ask useful questions of customers, propose designs, guide projects towards what was feasible and practicable, and bridge the gap between code and client.
These were supported by able Analyst Programmers, who worked at the sharp end to create what was needed but also - as the title implied - were expected to provide some thinking too.
Unfortunately, with SSADM being in effect the Maastricht Treaty approach to agreeing requirements and producing designs, their actual ability could never be fully applied, and on occasion they unwittingly ( and often unfairly ) took the blame for many inevitable disasters wrought in the name of ‘process’.
Those roles were largely abandoned towards the mid-to-late 1990s, when business realised that multi-skilled personnel were both difficult to source and expensive, and that technical people tended to scare the more flappable business customers by asking such unsettling questions as “why?”.
It was much cheaper instead to employ battery farms of obedient code monkeys, and draft in Business Analysts - sometimes from the same dark realms within which Consultants lurk, waiting to prey on the unwitting - who could talk to the suits in their own language and not daunt them with any worrying technicalities largely due to their being completely ignorant about IT.
This struggled along with varying degrees of success, largely through developers ignoring the analysts and everyone pretending that what was delivered was actually what had been asked for or, in some cases, was even what was expected.
When the disaster ratio stubbornly refused to decrease, and it was discovered that anything more complicated than Notepad appeared to be delivered both laden with technical debt, unable to integrate with anything else, and already legacy before it was actually deployed, the industry looked at itself in puzzlement and decided Something Must Be Done ™. At the same time, some of the older programmers reaching their technical ceiling of ability or at the end of any desire to move into either Management or Business Analysis were looking around for something new to do.
This led to the introduction of Technical Architects ( or Solutions Architects if they knew even less than that ), a role that to this day amuses and entertains generations of software professionals through its complete lack of any distinction or definition within the industry.
As a rule, these are ( or were ) highly technically skilled personnel who were either getting a little long in the tooth or distinctly bored with writing yet-another-database-system and so were instead elevated to supervise their peers. They were excused the need to deal with anything as trivial as details, but could instead loftily bridge the gap between the Business Analysts and Developers, whilst at the same time getting to draw hugely intricate, colourful and beguiling diagrams which no-one understood and which the coders would again ignore as either being a) unfathomable b) unfeasible c) hugely over-engineered.
And everyone was happy.
Req*UK/ * Stratford-upon-Avon