• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Translation Workflow Make or Buy?
 

Translation Workflow Make or Buy?

on

  • 670 views

 

Statistics

Views

Total Views
670
Views on SlideShare
670
Embed Views
0

Actions

Likes
1
Downloads
8
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Translation Workflow Make or Buy? Translation Workflow Make or Buy? Presentation Transcript

    • Translation Workflow Make or Buy? Business Process Analysis and Workflow Design Frank Bergmann, 2005-10-22
    • Contents Make or Buy? Examples/ Cases Rumors, Hype, Fashion ROI IT-Dept? Customer Relationship What to do? Why do it? How to do it? IT Provider & Evaluation Internal Efficiency Skills & Resources? Organizational Change Do we really need this? Cases Provider Relationship Which Parts/ Functionalit? Make or Buy textbook Strategic or not? Make case Buy case Adapt case Explain & define "Workflow" BizProcs Workflow Design Resources Eval Matrix Workflow Scoping What‘s in for me?
    • Why These Slides?
      • Reason #1: Understand ROI
      • Reason #2: Don't leave it to the Techies! (I‘m a techie!)
      • Reason #3: Know What You're Doing
      Do we really have to go through this?
    • Reason #1: Understand ROI Time Cash Flow Opportunity Occurs Project Activity Begins Opportunity Is Perceived Breakeven Time First Customers Are Satisfied Project Becomes Extinct Product Definition and Plans Freeze Product Is Released to Production (Mostly Product R&D) Positive Cash Flow Negative Cash Flow Net Profit Period Source: Strategic Issues in Managing Technology and Innovation, Anthony F. Chelte, Western New England College The negative cash flow (investment) depends on which workflows to implement and how . The amount of the positive cash flow depends on the gained efficiency
    • Reason #2: Don't leave it to the Techies System Stake Holders Spheres "Emotional" "User" How to use "logical tools" to analyze the "human issues"? "How can we get rid of all this task crap?" "Logicians" How to do the work? Text & Analysis: http://www. fawcette .com/interviews/beck_cooper/ Figure: ] project-open [ , own elaboration, http://www.project-open.com/whitepapers/ Client Analyst PM Dev. User CEO Dept.
    • Reason #2: Don't leave it to the Techies Project Manager The PM is the (only?) conflict mediator System Strategy Tactics Biz Needs Tech Needs User Needs Stake Holders Domains Profiles Text & Analysis: http://www. fawcette .com/interviews/beck_cooper/ Figure: ] project-open [ , own elaboration, http://www.project-open.com/whitepapers/ Client Analyst PM Dev. User CEO Dept. Func. Ana. Dev. User Biz Ana./ Consultant
    • Reason #3: Know What You're Doing
      • Technology is fashion business – it changes every 3-8 years
      • "Hypes" usually take a lot of attention
      • Most hypes contribute something, and leave their trace in the industry.
      • Some don't.
      Source: http://www.jboss.org/products/jbpm/stateofworkflow
    • Business Processes Source: Workflow Reference Model, The Workflow Management Coalition: http://www. wfmc .org/
    • What‘s a Business Process? A business process is the flow or progression of activities [...] Mike Havey each of which represents the work of a person, an internal system, or the process of a partner company [...] toward some business goal. Activity1 Start Activity2 End A sample Business Process in BPMN (Business Process Modelling Notation) "Deliverable" Source: ] project-open [ , own elaboration, http://www.project-open.com/whitepapers/ Gateway Condition2 Condition1
    • Business Process Elements
      • "Event"
      • Gateway
      • Activity
      • Artifacts (Documents)
      • Sequence Flow
      • Document Flow
      • Message Flow
      Activity1 Activity2 Source: ] project-open [ , own elaboration, http://www.project-open.com/whitepapers/ Start End Gateway
    • A Very Simple Invoice Example
      • Business Process Modeling Notation (BPMN)
      • Designed to be understood by business users
      Generate Invoice Send Invoice Close Invoice Receive Money Source: ] project-open [ , own elaboration, http://www.project-open.com/whitepapers/ Start End Invoice
    • Invoice Example (2) Generate Invoice Send Invoice Close Invoice Send Reminder Receive Money No Yes Cancel Invoice Source: ] project-open [ , own elaboration, http://www.project-open.com/whitepapers/ Start End Invoice Wait more?
    • Invoice Example (3) No Yes Company Customer Receive Invoice Check Invoice Send Money Wait for Money Send Correction Source: ] project-open [ , own elaboration, http://www.project-open.com/whitepapers/ Start End Start End Receive Money Send Invoice Generate Invoice Correct? Invoice Invoice
    • Sample Flash L10n Process Start No Modify Quote End Initial Contact Initial Analysis TM Analysis Quoting Customer Negotiations Yes Project Setup Prepare L10n Kit Trans lation Trans lation Trans lation Edit Edit Edit Inte gration Inte gration Inte- gration QC QC QC Delivery No Invoicing End Source: ] project-open [ , own elaboration, http://www.project-open.com/whitepapers/ Successful Negotiation? Source Flash Instructions L10n Report Text File(s) Wordcount Quote L10n Kit L10n Kit L10n Kit L10n Kit L10n Kit L10n Kit L10n Kit L10n Kit L10n Kit L10n Kit QC Report QC Report QC Report OK? OK? OK? Project-DB Feedback Report OK?
    • Business Process Description Languages Source: Mike Havey , author of Essential Business Process Modeling Standard Organization Type Business Process Execution Language (BPEL) OASIS Execution Language Business Process Modeling Notation (BPMN) Business Process Management Initiative (BPMI) Notation language Business Process Modeling Language (BPML) BPMI Execution language Business Process Query Language (BPQL) BPMI Administration and monitoring interface Business Process Semantic Model (BPSM) BPMI Process metamodel, in fashion of Object Management Group (OMG) Model-Driven Architecture (MDA) Business Process Extension Layer (BPXL) BPMI BPEL extension for transactions, human workflow, business rules UML Activity Diagrams OMG Notation language Workflow Reference Model Workflow Management Coalition (WfMC) Architecture XML Process Definition Language (XPDL) WfMC Execution language Workflow API (WAPI) WfMC Administration and monitoring, human interaction, system interaction Workflow XML (WfXML) WfMC Choreography (or similar to it) Business Process Definition Metamodel (BPDM) OMG Execution language and/or notation language, as MDA metamodel Business Process Runtime Interface (BPRI) OMG Administration and monitoring, human interaction, system interaction, as MDA metamodel
    • Workflow Engine Source: Workflow Reference Model, The Workflow Management Coalition: http://www. wfmc .org/
    • Workflow Process Elements
      • "Event"
      • State
      • Gateway
      • Activity
      • Artifacts (Documents)
      • Sequence Flow
      • Document Flow
      • Message Flow
      Activity1 Activity2 Source: ] project-open [ , own elaboration, http://www.project-open.com/whitepapers/ Start End Gateway
    • Invoice Example (2) Generate Invoice Send Invoice Close Invoice Start End Send Reminder Receive Money No Yes Cancel Invoice Source: ] project-open [ , own elaboration, http://www.project-open.com/whitepapers/ Invoice Wait more?
    • Invoice Example (2) With States Generate Invoice Send Invoice Close Invoice Start End Send Reminder Receive Money No Yes Cancel Invoice Source: ] project-open [ , own elaboration, http://www.project-open.com/whitepapers/ State Diagram / Petri Net Invoice Wait more?
    • What's the difference?
      • The "State" concept allows your IT guys to put this description into a computer system (specification)
      • "States" won't work in high-level process designs. It forces the business analyst to get down to "reality"
      Source: ] project-open [ , own elaboration, http://www.project-open.com/whitepapers/
    • Status Engine Example
      • The diagram shows a status engine according to the business process that we have defined before.
      Receive Money Waiting for Money Money Received Generate Invoice Start Invoice Generated Send Invoice End Cancel Invoice Invoice Unpaid Close Invoice Send Reminder Timeout Source: ] project-open [ , own elaboration, http://www.project-open.com/whitepapers/
    • Question to the audience
      • Let's imagine we really want to implement this workflow using a Workflow application:
      Receive Money Waiting for Money Money Received Generate Invoice Start Invoice Generated Send Invoice End Cancel Invoice Invoice Unpaid Close Invoice Send Reminder Timeout Source: ] project-open [ , own elaboration, http://www.project-open.com/whitepapers/ Should we allow the Accountant to reset the invoice status to "generated”? Should the accountant be able to skip the invoice? What will happen to the $$$?
    • Further Questions
      • Should everything be allowed ("collaboration style”)?
      • When?
      • Why not?
      Waiting for Money Money Received Start Invoice Generated End Invoice Unpaid Source: ] project-open [ , own elaboration, http://www.project-open.com/whitepapers/
    • Group Work: Design the Status Engine Waiting for Money Money Received Start Invoice Generated End Invoice Unpaid Source: ] project-open [ , own elaboration, http://www.project-open.com/whitepapers/
    • Workflow Design
    • "Fine Grain" or "Coarse Grain"?
      • Small Company:
      • Company specialized on Flash:
      • Your Company: ???
      Start Flash L10n End Source: ] project-open [ , own elaboration, http://www.project-open.com/whitepapers/ To what degree should a company enforce the order of steps and the assignment of tasks of a process?
    • "Fine Grain" or "Coarse Grain"?
      • Workflow implementations behave like other IT investments
      • Fine grain workflows have higher initial and setup overhead costs
      • The optimum granularity depends on many factors
      Fine Grain Coarse Grain Up-Front Investment Overhead per case Cost per case Optimum ROI Source: ] project-open [ , own elaboration, http://www.project-open.com/whitepapers/
    • Process Implementation Styles
      • "Email" Style
        • No workflow at all, documents are sent around by email
        • Pros: Flexible, no investment, "ad hoc"
      • "Collaboration" Style
        • Online Forums, common filestorage, ...
        • Pros: Flexible, low investment
      • "Organizational" Style
        • Fixed process, but order is maintained informally.
      • "Prescription" Style
        • Formal workflow
        • Pros: Formalized, Standardized, Reporting & Metrics, ...
      Activity 1 Activity 2 Activity 2 Source: ] project-open [ , own elaboration, http://www.project-open.com/whitepapers/ Trans. Workflow Projects Users Clients Costs Data Ware- House File Storage Project Forum Quality Sales Provider Mgmt. Invoicing
    • Workflow Design Criteria
      • Workflow design takes a Business Process and creates an IT application from it.
        • "Fine grain" or "coarse grain" implementation
        • Email, Collaboration or Prescription style implementation?
        • Short or long-lived processes?
        • Reporting & Workflow Metrics
        • Flexibility
        • Security & Permissions
        • "Trust Model"
        • "Water-tight" processes vs. Human Decisions?
        • Botton-Up or top-down design?
      Source: ] project-open [ , own elaboration, http://www.project-open.com/whitepapers/
    • End Frank Bergmann frank. bergmann @project-open.com www.project-open.com