|
|
| (19 intermediate revisions not shown) |
| Line 1: |
Line 1: |
| - | [[Category:IT]] | + | [[Category:Alex]] |
| - | | + | |
| - | == About ==
| + | |
| - | | + | |
| - | == March ==
| + | |
| - | | + | |
| - | == itn1 ==
| + | |
| - | === New Strategic decision about "Holistic approach to IT and Web systems" approved by Simon ===
| + | |
| - | | + | |
| - | IT Support coordination will be a responsibility of "Product and Support team".
| + | |
| - | It is a change because up until now they handled only CT2 support.
| + | |
| - | | + | |
| - | Disadvantages:
| + | |
| - | * additional responsibility that requires time
| + | |
| - | * lack of knowledge and experience
| + | |
| - | ** Tira is strongly qualified (BS in Comp Sci; Master in Info Management Systems; Network certification)
| + | |
| - | ** Tracie and Denise are beginners in IT
| + | |
| - | | + | |
| - | Advantages:
| + | |
| - | * increased value to Jaguar and Market = increased job security
| + | |
| - | * opportunity to gain new knowledge
| + | |
| - | * opportunity for Holistic approach (treating IT and CT2 as a whole, not fragmented); examples:
| + | |
| - | ** full vision and control over user/systems interactions and work flows
| + | |
| - | ** more services could be integrated into CT2/Cloud like web folders;
| + | |
| - | ** integration between CT2 and non CT2 system like Sugar and CT2
| + | |
| - | | + | |
| - | Transition agenda:
| + | |
| - | * phase 1 to be completed by the end of March
| + | |
| - | * Jaguar IT support knowledge exchange (KE)
| + | |
| - | **2a IT documentation: [[blog11]], [[notes11]], wiki IT category
| + | |
| - | **2b regular KEs
| + | |
| - | * Career plan for BAs:
| + | |
| - | ** agreement on responsibilities, goals and developmental stages
| + | |
| - | ** Formal IT training
| + | |
| - | | + | |
| - | == itn3 ==
| + | |
| - | === Who is Who and Vendors list ===
| + | |
| - | | + | |
| - | This info is maintained in [[Vendors IT]]
| + | |
| - | | + | |
| - | == itn4 ==
| + | |
| - | === IT documentation ===
| + | |
| - | | + | |
| - | All wikis related to IT are in [[:Category:IT]].
| + | |
| - | | + | |
| - | [[IT Support MAIN WIKI]] has up to date instructions on how to navigate this directory.
| + | |
| - | | + | |
| - | | + | |
| - | == itn5 ==
| + | |
| - | === Desktops and users info (NY office) ===
| + | |
| - | | + | |
| - | It is managed xls attached to this Mantis: 0002803: ** Desktops and users info (NY office) **
| + | |
| - | | + | |
| - | Please add columns as required (MS office version, etc)
| + | |
| - | | + | |
| - | Every time document is changed new version is attached.
| + | |
| - | | + | |
| - | == itn6 ==
| + | |
| - | === March is a month of Support ===
| + | |
| - | | + | |
| - | To: Tira, Tracie, Andrei
| + | |
| - | | + | |
| - | From: Alex
| + | |
| - | | + | |
| - | Upper management brought to my attention that number of complex and critical bugs is increasing.
| + | |
| - | | + | |
| - | This makes experience of end users very painful and leads to a lot of frustration on the part of our clients.
| + | |
| - | | + | |
| - | We need to resolve this rapidly.
| + | |
| - | | + | |
| - | I believe that this happens due to the following reasons:
| + | |
| - | | + | |
| - | * growing list of new interrelated features increased system complexity significantly
| + | |
| - | * we are introducing new changes rapidly and without careful analysis (focus on quantity not quality)
| + | |
| - | * most people on our team have only minimal understanding of CT2 components outside of components they "own"
| + | |
| - | * not enough verbal communication between all members of the team particularly with developers
| + | |
| - | * non technical BAs and MOs make bad design decisions and force them into development
| + | |
| - | * SAa are doing often a poor job and creating analysis that has critical errors
| + | |
| - | * MO-BA-SA-Dev-QA-BA is too long and too linear (no cross communication or group communication)
| + | |
| - | | + | |
| - | How to resolve this:
| + | |
| - | | + | |
| - | * focus on quality not quantity
| + | |
| - | ** do not rush adding many enhancements
| + | |
| - | ** add components after you selected best design and fully understand impact on the system
| + | |
| - | | + | |
| - | * focus on support:
| + | |
| - | ** every BA, SA, QA must understand 95-100% and be able to investigate EVERY module
| + | |
| - | ** all components should have complete, correct and readable documentation
| + | |
| - | | + | |
| - | * move systems design from BA&Support Team to Dev Team
| + | |
| - | | + | |
| - | * more verbal communication between all members of the team developing components
| + | |
| - | | + | |
| - | * improved soft dev process:
| + | |
| - | ** Architect to review all tasks at various stages of BA/SA/Dev
| + | |
| - | ** Joint Design sessions early into BA stage, during Design and at the end
| + | |
| - | ** low impact changes/projects could be documented by BAs; SAs are on as needed basis
| + | |
| - | ** high impact changes/projects must be run by technical staff (SA or Developer); BAs are on as needed basis
| + | |
| - | ** For med/large and high impact projects:
| + | |
| - | *** BA team must submit RFPOP (Request for proposal or prototype) to Dev team that contains ideally only high level requirements
| + | |
| - | *** Dev team should in return communicate proposal or prototype
| + | |
