Friday, February 15, 2008

Visual Studio 2008 training kit Business Analyst perspective



URL
XMLFILE

03 Business Analyist Perspective.wmv 2ac06089-956c-420c-96df-8ece50fc5c30 -3.79050565 ok so -2.50975505 module 0.3011792 business analyst 6.679898 process methodology 11.4312937 developing vision 15.24429485 gathering requirements 20.11746945 first of all 22.64999555 first lesson 25.99690595 ways techniques 28.49756695 requirements 32.0896429 vision statements 37.0899774 before state 41.09052835 any farther 44.18351025 clear vision 45.9971497 measure 47.84048195 successful 50.52746945 stakeholder 53.8422756 repeat recite vision 57.717813 clear tend short 60.905169 essays 64.43791275 nice short clear concise 68.27897285 project 70.9072041 progresses 74.2820239 initial set of goals 81.7215953 focus on common goal 88.94043205 two broad categories 92.46874155 strategic projects 99.43924265 predecessors 103.2870545 most useful 106.7537087 elevator pitch 111.0661667 recited short duration 114.2854105 contrast 117.22574725 adaptive projects 120.5370749 aim tackle 123.41059865 incremental change 127.00639235 vision statements 131.07154875 business process change 134.4458413 business process 136.66391845 perspective 140.50985945 regardless of type 144.66783225 captured 148.60458735 clear on vision 152.2609808 capturing 154.69828915 requirements 157.1672041 danger 159.4492472 too many 162.1685477 upfront 164.7318674 too detailed 169.54371205 lead to 171.1683583 stalling 175.88735835 analysis paralysis 179.63657035 getting enough 183.922288 not getting stalled 186.79679825 every single 190.04647965 only start 194.4859354 new requirements 196.7354048 appear 199.0774808 value up approach 203.42131295 business environment changes 209.01913155 capture upfront 212.5798901 end of process 215.33171885 business space 217.92474495 problem space 221.48879365 assertion 224.52049665 knowledge 226.39393655 changed 228.30264855 changes 231.11456805 chances change 236.27094335 effectively handle change 240.27032655 limit number of 243.43036175 requirements 247.5538549 very difficult 250.4597642 focus subset 254.1813538 iterative development 258.4313776 next 261.86775625 working through iteration 265.49210095 new use cases apparent 268.71636175 additional feedback 271.46273705 based unit of 273.8055964 deliverable 276.1825647 mistake 279.1859513 try and capture 282.90266215 balance right 286.68299555 level of detail 290.1222597 individual 293.0294626 definition 295.9689309 x axis 298.3107064 ambiguity 302.59389685 concise clear 306.2163232 understandability 309.90668485 sweet spot 313.9981191 precise well specified 321.12498985 understandable too much detail 327.7516225 intention behind requirements capture 333.9076894 understandable either 337.6589842 granularity 340.4693243 specific 344.44118485 successful project 347.9735409 all roles involved 350.81829255 understand 353.81747965 same set of requirements 357.50487195 misalignment 360.41097965 individuals 362.9101032 understand 366.6293447 granularity 370.91140935 functionality 373.97544785 that stage 379.06906695 test driven development 383.47695695 advocates 387.72595015 forcing developers to think about tests 391.75859415 forces to think 395.6649649 about requirements 399.73070415 test unless 403.41609075 detailed understanding 407.19740255 developers starts 410.5128549 higher degree 413.2605953 granularity 416.6683538 requirements 420.6707132 high priority 424.32578465 useful technique 428.14103745 idea using stack ranking 432.35956805 put priorities 437.2673266 problem tends to come 440.48558395 think of 444.01575515 priority 1 must haves 448.20635495 how to prioritize 451.8273334 big subset 455.1128073 one requirement 457.86133675 against another 460.76774385 both must haves 464.20567575 this one more significant 466.98776425 rankings 469.57977895 requirements in order 473.5823606 set of requirements 476.301542 tackling 478.4912291 next iteration 480.9583776 gather track 482.92698985 scenarios 487.17674725 quality of service 490.71234815 non functional 494.0849876 transactions per second 497.9909445 concurrent users 500.93018145 scalability 502.70962135 security 505.05407035 usability 506.58789235 track 508.64736625 functional requirements 512.7147892 non functional 516.02584585 different type 518.46099555 work item 520.4336418 database 522.3061826 implementation 525.77662365 specific features 529.99421775 testing for 532.84244445 satisfies 535.68389915 upfront 538.5278935 work items 541.5907665 msf agile template 544.59184925 work item type 547.8416225 capture requirements 550.87364175 this point 553.21971775 pause video 556.27996945 perform exercise 559.6893504 accompanies module 563.09241505 series questions 567.6582041 types of requirements 571.81292405 effective techniques are 575.34474385 level detail 578.00226195 granularity 582.2190851 exercise also encourages 587.1907971 projects haven’t turned out 591.53634245 divergence understanding 595.4729264 different stakeholder 600.9743912 spend five ten minutes 612.13110885 considered requirements 615.9743039 this lesson 618.72661115 personas scenarios 623.57089005 concepts used by msf 627.4459014 descriptions 630.13404995 users of system 633.04084925 represent scenarios 636.32036965 system building 638.60500685 personas 640.94717575 essentially 643.2601769 representation 645.5717642 user of system 648.4809309 more detailed 651.2907846 than actor 657.48163385 brings definition alive 663.54473245 interact with system 665.98240935 considering 668.4499536 personality 671.13873815 work environment 673.79763835 single actor 676.8896123 represent end user 681.1403833 multiple different types 686.7340885 subtly different ways 692.04751705 slightly different benefits 696.1439683 user interface 700.04774835 they want to interact 702.9247155 personas 705.89403975 extra detail 708.42433455 name 710.83222225 team 711.92366675 users 716.70707035 refer persona via name 720.9874513 real benefit 724.77137645 use cases scenarios 729.39449665 separates developer from 734.99099665 applications real customers 739.3644706 easier to discuss 743.0852699 role play activities 746.68020415 artifacts 749.08786285 automatically 752.5862268 word document 755.6196837 definition 757.55516785 example 759.3681951 guidance 762.49412475 template instruction 766.93127785 fill out persona 772.0283708 analysis 776.62367125 captured definition 780.2159808 scenarios 782.4962824 msf captures 786.3401769 persona interacts 789.1251055 system 791.03143995 achieve goals 793.65532885 series steps 797.68508285 three things together 801.2817234 capturing 805.2200919 identifying goal 808.9391202 decided 811.09423245 nailed down goal 813.719415 list of steps 816.5951656 does step 1 820.75220185 breaking down 823.72058395 persona go through 827.56606125 write in language 831.7828776 end users understand 834.879788 validating 839.22217805 techniques 841.3182007 end user 844.31906245 exactly in mind 848.10066105 scenario on track 852.06968935 not system language 855.50800235 really understanding 858.0391248 captures 859.79082775 recommendation 862.22650345 detail 863.6314842 alternate 866.47722905 concentrate upfront 870.56956805 positive scenarios 874.0717177 exception cases 877.13520755 behaviors 879.9772302 occur 882.0414989 system 884.07198075 once captures 888.760398 valid scenario 890.9171032 interviews 892.79255675 end users 896.01278235 validation scenarios 900.23050685 enough scenarios 903.0441497 map back 905.07532885 full end to end 907.88990705 solution story 913.32874265 covered by requirements 918.70310205 complete coverage 922.4520545 validate scenarios 925.45253065 customers 929.0492937 meaningful feedback 933.23707715 requirement in mind 935.70454765 validate 937.23687535 scenarios 938.92361685 additional 942.11418825 test team 947.5506361 detailed enough 954.95605335 fulfills 956.80146265 negative 959.7714876 failure condition 962.1440216 pin it down 964.89759075 validate scenarios 968.8980862 specific behaviors 971.74156465 system 975.773483 capture requirements upfront 980.9002914 implementation 984.65111795 angle think of 988.30534355 architect developer 992.6500397 interfaces 994.83693545 dependencies 999.7740318 go ahead implement 1004.21623475 break scenario down 1007.68249665 work item task 1011.7774819 link task up to scenario 1015.99482545 well enough 1019.2144649 scenario definition 1024.5622234 validations need to do 1028.2162109 thinking about 1031.43537535 scenarios should be 1038.0624343 requirements change 1041.2183266 evolve 1043.0944819 through 1045.594779 lifecycle 1048.346559 capturing 1051.47003855 wow factors 1055.21974265 key scenarios 1058.1876871 initially create 1060.7509241 out early 1063.9401837 extend modify 1067.4076622 more feedback 1070.90886855 look developed 1075.2569048 additional scenarios 1079.19046375 later iterations 1082.2553674 move forward 1085.19213045 more scenarios 1089.50617805 dissatisfiers 1092.4143708 antipatterns 1096.63341165 review 1100.5055817 every project 1104.63358735 vision 1107.7277971 recite well 1110.69585155 understands 1113.91360435 capture requirements 1116.91535265 using scenarios 1120.8216758 develop scenarios 1123.13532545 personas 1126.5115783 specific requirements 1131.3550397 also think about quality 1136.54335035 maintainability 1139.76245245 vsts 567.25528345 work items

No comments: