Pega Business Architect 7.4

Business Architect - answer-- Define *business rules, SLAs and processes* - Advocates for business users - Work with SMEs and stakeholders to understand business needs and define uses cases & features System Architect - answer-- Object oriented design and technical implementation skills - Configure application assets such as UI forms and automated decisions Stake Holders - answer-review, refine and approve the solution SMEs - answer-work with business and system architects to create metaphors that represent your business processes Case Designers - answer-SMEs, BA, SA, Stakeholders DCO - answer-- capture business requirements - DCO help increase speed and accuracy of application delivery - Helps technical and non-technical people communicate Purpose of Best Practices - answer-- Well defined methods or techniques that lead to desired results - Every best practice has at least one goal - Proven to make progress towards achieving goals Best Practices - answer-- Leverage DCO to improve product quality - Use standard Pega capabilities - Iterate and test as you build Iterate and test as you build - answer-- Use most agile and iterative delivery model available for your org - First separate large applications into smaller more manageable components - Build and test individual process incrementally - Analysts test the application to make sure the application meets the requirements and business objectives Daily... - answer-standup meetings to set priorities for the day, ensure alignment, and eliminate any blockers Weekly... - answer-project updates to track issues and update the status report; flag conditions that need immediate attention Biweekly or Monthly... - answer-meetings to review the entire project and determine whether the application conforms to the original design objectives Guardrails - answer-- Guardrails help ensure that you use best practices for configuring Pega apps - Standard guardrail capabilities that enable development team members to track compliance with - Pega best practices - Easier to maintain and upgrade and have fewer defects Role of BA - answer-- Scope and customize application releases - Bridge between IT and business - Should focus on gathering requirements that help customize standard application - Define business rules Journey Centric Delivery - answer-- Frames application delivery around case types - Scrum preferred - Product owner is user of application - Product Sponsor is often an executive with the vision for completed application - BA and SA are part of Scrum team for delivering application - BAs are part of testing and configuration - Are organized into a series of releases with a target of 90 days (minimum lovable product) - More specialized releases defer to a release pattern of 45-60 days MLP - answer-- Use standard case types Kickoff - answer-- Review scope of the first release and defines a roadmap for future releases - BA joins as kickoff is preparing Steps in Journey - answer-Prepare, Build, Go Live How BA participate in JCD - answer-- "Refine the backlog of user stories, planning sprints, developing features and reviewing completed configs" - Project starts during the sales cycle -- BA typically not involved in this part BA responsibilities and activities - answer-- Customer prioritizes the collected backlog to define the 1st release - Product owner then creates the ACs for the 1st release w/ members of delivery team - BA begin during the backlog refining and continue through sprint planning and delivery Backlog refining - answer-- BA refines user stories for upcoming sprints - Refining process ensures that the description and AC reflect what team must deliver - There should be 2 sprints worth of user stories ready at anytime - Planning - answer-- At beginning of sprint decide which user stories will be pulled into sprint - Assign owner to the user story and sets end of sprint as due date - Help product owner assess the status of the release Delivery - answer-- As developers finish work, configurations should be tested and reviewed with the product owner ASAP - Project features are tested against ACs - Once product owner determines config is good against ACs team members begin work on another user story Agile Workbench - answer-- Use Agile Workbench to capture user stories, bugs and feedback items - Using Agile Workbench, walk through each stage of the case type with business stakeholders and product owners and record bugs/enhancements (user stories)/feedback Work Status - answer-- To-Do - Doing - Done Feature Parts - answer-- Has feature name - Count of subfeatures - Progress indicator Benefits of Features - answer-- "Features help stakeholders identify the product components that are being built and visualize how the components fit together" If marked rejected, show up as __________. - answer-Done Case - answer-- work that delivers a meaningful business outcome - organized into high level milestones called Stages Life Cycle of Case - answer-how to manage the case as it is opened, worked on and resolved Case Types - answer-- (template) is an abstract model of a business transaction, while a case is a specific instance of the transaction - defines data structures, processes, tasks and user interfaces to process transaction Stages - answer-- the first level of organizing tasks or processes -- organize case life cycle around key events that support goal - further organized into processes which define one or more paths the case must follow - Change in status of case and owner Processes - answer-contain a series of actions or steps to complete to resolve case Primary Stage - answer-Stages that lead to expected outcomes Happy Path - answer-A sequence of primary stages Alternate Stages - answer-- When work does not go according to plan use an alternate stage - Used to organize steps that are not part of the "normal course of events" - Ex. cancellation stage Naming stages - answer-Use a noun or noun phrase -- limit to no more than 2 words Number of stages - answer-- Only 7 primary stages - Need more than 10 primary stages? Create new case type or combine stages - Only 5 alternate stages - No minimum number of stages for a case -- try to have less than maximum number of stages Stage transitions - answer-- primary stages, automatically go to next primary stage after all process steps completed - Controlled transition Add Controlled Transition - answer-- to go to next other stages before completion of current stage -- can be added to any primary stage or alternate stage - Can be action in a step or a specific step in process - Can allow a user to select stage to which the case transitions -- *most useful in Yes/No decisions* - For example if Yes selected continues to next primary stage - Can be added using the Change Stage smart shape or as an optional user action