Analyst Flashcards
appian do’s
provide business value limit time scope (rapid time deployment) showcase software (UI) solves pain point lack of collaboration -> news tab visibility -> interface automation -> process models
appian dont’s
complex integration
poorly defined requirements
large data transformation
replace system without improvements
HR -> Form -> Database
bad idea, just moves data
Analyst
Defines user roles and responsibilities bridge between business users and app developers make requirements clear for everyone prototypes of records, reports, news writes acceptance criteria
Designer
Builds the application
- configure records, reports, forms, processes
- relational db schemas and views
- deploy to test or production environments
lead designer
Designs the solution that meets analyst requirements and performs at scale
- does everything designer does
- design solution that meets requirements of analyst
scalable, maintainable, intuitive application
- db integrations between appian and other systems
developer
Builds custom plugins in Java
- custom java plugins when no feature exists
functions
smart services
cdt
servlets
- setting embedded interfaces using js in external portal
tester
Makes sure what a designer builds fuctions correctly to meet analyst requirements
- test scripts
product owner
Prioritizes the backlog
- what will go on backlog, priorities, and when they will be delivered
scrum master
Removes blockers and ensures that the team follows an agile methodology
using agile methodology, keeps ppl on track
definition of done
A user story should meet these criteria before it can be considered complete
- unit tested
- code review
- documentation written
story points
A way to measure the complexity of work
user stories
Describe a requirement from the user perspective
something user can do and covers functionality that needs to be built
as a i want to , because
backlog
Prioritized list of features that need to be delivered
definition of ready
A user story should meet these criteria before it can be included in a sprint
- story points assigned
- story written
- test plan defined
- acceptance criteria defined
sprint review
Meeting held at the end of each sprint to go over what was accomplished
acceptance criteria
Defines the parameters of a feature and adds detail to a user story
- each user story needs to meet
- add details to basic user story
- understand specific needs of end user
- analyst responsible for writing acceptance criteria
sprint
Defined period of time when work gets done
1-4 weeks where work gets done (2 weeks for appian)
- created shippable product, no matter how basic it is
agile
small quick releases rather than delivering large application at the end
split project into smaller releases to deliver the most value
does appian work well with agile?
yes, works well with small iterative releases
- more stakeholder involvement
frequent custom demos
respond to changes more quickly
scrum
type of agile method
iterative process for managing applications
daily meeting, sprint review, sprint retrospective
daily meeting (standup)
answer 3 questions
what did you do yesterday?
what are you doing today?
are there any blockers?
sprint retrospective
happens after sprint review
allow team to discuss what they can improve to make next sprint productive
scrum roles
product owner
scrum master
developer
example user story
as a student, i want to buy a parking pass, because i want to drive to school
- small enough to complete multiple in a single sprint
epics
- many stories and spam multiple sprints
- represent larger requirement
- doesnt need to be completed in single sprint
tools for agile
physical (whiteboards with backlog sprint dont on it)
jira pivotal tracker move cards track velocity of team how much they can get done in a sprint viewing record of what was done reporting on the team metrics
sprint 0
plan and define logistics of the first application release
- does not provide shipable product at the end
- purpose is to identify project goals and define release plan
- dont need to provide high level detail of user stories
important time to work together
actions that happen during sprint 0
chartering, sprint cadence, personas, story mapping, defition of ready/done, story sizing
chartering
- team given high level overview of what project is, why its being done, and the goals
- end of sprint 0 should have a charter
sprint cadence
how long sprints will be
personas
- define roles of users that will interact with application
- knowing users will drive user stories
story mapping
- break down high level requirements into smaller stories that can be more effecitvely prioritized
- visual representation of project requirements
- helps with logical order of stories that go into the backlog
story sizing
points dont represent time it takes to get story done, just complexity and difficulty
gathering requirements
user roles, defining data
GR defining data
- record (central object working around)
- process built to affect the data
- reports driven by what data you collect
where:
data come from 3 places (relational, internal, external)
what do you want to collect?
define data in process flows
store in temporarily or store it in db
analyst mode
drawing out process flow and define what tasks should happen and what conditions to meet when there are decision points
designer mode
configure process model diagram and make it work
scirpt task
system work
user input task
task users can complete
gateways
divert process flow
swimlanes
organize flow in logical manner
what helps clarify a process?
swim lanes and annotations
types of charts in reports
pie, bar, column, line, grids
how to get data in reports
sql queries, expressions
interfaces
- maximum of 2 columns
- buttons show up left or right
- text black, error is red
- rich text for style text
- appian style guide for interface designers
mockups
understand how user interact with interface (web or mobile)
editable grid better on desktop view than mobile
news posts focus
- make sure always targetted to specific group
- shouldnt be log of everything that happened in system
- use exceptional events/escalations to alert wider groups
- can also target one person (loan request denied)
when to use tempo
if user needs to make decision over applications
- full access to news
- start many actions
- records/reports
when to use sites
one application focus
- actions/record lists/reports
- news cannot be accessed in sites
weapping up development
test based on acceptance criteria. analyst makes sure features properly tested (high impact functionality, bug fixes)
who writes out the test cases
analyst since they are the expert on the team for business requirements
end of sprint demo
user story finished: demo each functionality ensure isntant feedback changes can be picked up quickly product owner or designers can give demo
who are the business users
target audience for demo
make sure it goes over their needs
tell show tell technique
tell them what they are going to see
show them what you told them they are going to see
then tell them what they just saw
keeps presenter on track
how to keep on track during demo
use a script
demonstrate value at the beginning
start with best features first
capture their attention
can users use platform after deployed?
yes, users should be involved in frequent demos to make sure they get what they want and need
appian quick reference guide
help end users to understand appian interface
choosing next project
make enhancements to previous projects,
objects in appian can be reused across applications
decision designer
allow users to create test and manage business rules without using any code
conditions
business rules defined
what can decision be used for?
used for what process to start next or who to assign task to
DD unique
all decisions need to be unique (no overlap)
only output single hit
DD first
can be overlapping data, but return first one it hits
DD rule order
can be multiple hits, output every single one in order they were hit
naming for decision designers columns
useCamelCase
choice label
what they see
choice value
value represented by label
appian object data types
process,folders,users,groups
objects that support an application
naming for expression/decisions
PascalCase
who can make decision designer
analyst or designers
when you use a qeury rule or expression rule to define the value of a dropdown in your decision, rule executed during design time (in decision designer), does not get re-executed during runtime
True
create grid image column
a!gridImageColumn( label: "Category", field: "categoryId", data: a!forEach( items: index(local!datasubset.data, "categoryId", null), expression: a!documentImage(document: rule!VMR_DetermineCategoryIcon(categoryId: fv!item)) ) )
