You're about to create your best presentation ever

Lifecycle Presentation Template

Create your presentation by reusing one of our great community templates.

PGT Lifecycle Presentation

Transcript: Student Demographics Faculty of Education A: Establish a PGT Team Create new culture of PGT in Faculty Clearer lines of responsibility Greater collaboration Increased commitment Higher task performance B: Implement online application for PGT Inline with sector move towards fully online applications Save time and resources across functional areas Audit trail of approval process will assist with future Departmental Reviews. Team Leadership Model Identify existing skills and knowledge AUGUST Verbal Communication Schein (1990a) Consultancy Project: Review your ability ratings Change Management Flatt (1992) Objectivity Personal Development Plan Timeline MAY FEBRUARY 2014 SEPTEMBER 2014 D. Enhance Induction / Transition process Lifecycle of a Postgraduate Taught student in the Faculty of Education at Liverpool Hope University Second Life Areas for Development Repeated processes within Application stage Tutors have little knowledge of Induction process International student numbers increasing New staff and tutors new to PGT running modules in 2014-15 Changes to Research phase not disseminated to staff No formal dissertation guidance for students or staff Assess different scenarios and make confident decisions Watson (2011) ; Watson (2013) Decision Making Staff Demographics About Me Key Personnel: Newton (2010) Rawson, Duncan and Jones (2013) Future development Hill (2010) PGT is on the periphery PGT does not entirely fit within Faculty structures Tacit knowledge needs to be shared Wider PGT team not defined Charities / Not-for-Profits / Christian organisations Digital Media Projects Second Life Website redevelopments My skillset PDP Schein (1990b) Change Management Consultancy stages Research Skills Victoria Grimbly Technological Rate your ability Benefits: A. Establish a PGT Team PGR online application system UG ‘induction app’ to be released Student Transition Expert mode + Doctor-Patient mode Independent and unbiased observer About the Project End to End Journey : B. Implement online applications for PGT Recommendations Lack of coordinated marketing and communications plans Applicant data is not readily available Applicants are not ‘kept warm’ by Faculty Modules are run with non-viable numbers Module evaluations are a duplication of PTES What is the PGT Lifecycle? Consultancy approach Literature Thank You C. Improve the Admissions process Conduct face-to-face interviews Operational Admissions through to Graduation A postgraduate student's journey within the Faculty of Education Schofield and Sackville (2010) C: Improve Application process Improved decision making within PGT area with shared applicant data Greater retention of applicants through to registration stage Improved provision with viable student numbers on modules D: Improve Induction / Transition process Induction app to used by wider student base Building block for improved framework of induction Organisational Culture Professional and Ethical standards Strategic Deliver a presentation without extensive notes Identify future knowledge and skills Recommendations About the Organisation Hill's model for Team Leadership (Northouse 2010) MAY SEPTEMBER 2014 AUGUST FEBRUARY 2014 Research Skills Objectivity Independent and unbiased observer Decision Making Verbal Communication Deliver a presentation without extensive notes Conduct face-to-face interviews Assess different scenarios and make confident decisions Personal Development Plan Timeline Findings

The Wheel: A Lifecycle Template

Transcript: The Wheel: A lifecycle is a structured framework consisting of a series of stages and corresponding activities—such as analysis, design, implementation, and evaluation—that characterize the course of evolution of, in this context, the full evolution of an interaction design or a complete system or product. Iterative Process An iterative process is one in which all or part is repeated for the purpose of exploring, fixing, or refining a design or the work product of any other lifecycle activity. It is the “wash, rinse, and repeat” characteristic of HCI. Understanding the Concept of Process The Design Phase lvl1.1 Information architecture lvl1.2Conceptual model design lvl2. Macro lvl3.Micro UX Lifecycle Template it's all about understanding user's work and needs Universal abstract activity cycle Project Parameters: Inputs to the Process Choices *risk tolerance *project goals *type of system being designed *development organizational culture *stage of progress within project System Ecology the context provided by the surrounding parts of the world with which it interacts. Task Structure Mode; it's the hierarchical decomposition of tasks and sub-tasks showing what tasks are to be supported and the relationship among them Task Interaction Model is a step-by-step description, including task goals, intentions, triggers, and user action. Understand user work and needs Understand the concept of a UX lifecycle process and the need for it. lvl1 lvl2 Know the key team roles in the UX process for producing interactive products Create interaction design concepts user researcher Implement Understand the process choice tradeoffs based on system type, domain complexity, and interaction complexity within the system complexity space Okay! Here we go! ANALYZE Analyze MICRO: detailed UX Design A PROCESS IS NOT NECESSARILY RIGID MACRO: Page design standards lvl3 subject master expert Evaluate Realize designs alternatives UX manager Understand how to identify project parameters and map them to process choices Design EVALUATE this is about the visual aspect and page content. Contents like headers and subheader,forms design, use of colors cues DESIGN Verify and refine interaction design Understand the “Wheel” UX lifecycle abstraction template interaction designer PROTOTYPE Without the guidance from an interaction design process, practitioners are forced to make it up as they go along. An approach without a process falls the whole project into the cracks. The people without the process are limited by their own experience and will just use and apply same techniques over and over for each project. Appreciate the need for choosing a process instance for your own project. visual designer correctly and consistently applying standards A LIFECYCLE TEMPLATE Without the guidance from an interaction design process, practitioners are forced to make it up as they go along. An approach without a process falls the whole project into the cracks. The people without the process are limited by their own experience and will just use and apply same techniques over and over for each project. technical writer Things we're going to learn.. OBJECTIVES dont freak out.. we can do this....... Process connotes a set of activities and techniques Lifecycle suggest a structure and shows series of change A process is a guiding structure that helps both novices and experts deal with the complex details of a project. Process acts as scaffolding, especially for novice practitioners, to ensure that they are on track to a quality product and on the path to becoming experts. Process acts as a checklist for experts to make sure they do not miss any important aspects of the problem in the heat of productivity. A process helps designers answer questions such as “Where are we now?” and “What can/should we do next?” A process brings to the table organizational memory from similar previous efforts by incorporating lessons learned in the past. In other words, process provides a repeatable formula to create a quality product. Process also alleviates risk by externalizing the state of development for observation, measurement, analysis, and control—otherwise, communication among the project roles about what they are doing is difficult because they do not have a shared concept of what they should be doing. Why do we need process? Sample of UX team interactive prototype programmer is a specification of the navigational structure of a Website. Non-visual aspect Information architecture presenting information architecture visually. Visibility and clarity are the keys. Also persuasion. Knowing your target audience, your identity and brand, creating atmosphere. Conceptual model design

LifeCycle presentation

Transcript: LOAD_CONFIGURATION SetupLocalizationManager SetupAuthentication SetupModelSupport SetupPurgeManager SetupRestClient ValidateMapiVersion SetupActivityMonitorRestClientAdvisor SetupCommonHeadersRestClientAdvisor SetupSecurityRestClientAdvisor SetupServerTokenValidatingRestClientAdvisor SetupTimeoutRestClientAdvisor SetupKeepAliveRestClientAdvisor SetupDelayOn503ResponseRestClientAdvisor SetupHandleRetrieveNonExistingEntityRestClientAdvisor SetupUniqueQueryCounterRestClientAdvisor SetupClientManager SetupListener SetupProxyFactory SetupLocalStorage SetupModel SetupAmbientTransactionManager SetupLazyLoadHelper SetupObservableInterceptor/SetupListenerDisallowedObservableInterceptor SetupMarkAsDirtyInterceptor SetupAmbientTransactionInterceptor SetupSwitchTargetInterceptor SetupLazyLoadingInterceptor SetupEventSource SetupEventDispatcher SetupMapiTransactionEventReceiver SetupHeartbeatEventReceiver SetupHttpProxyRequestEventReceiver SetupNetworkStatisticsManager GET_CONFIGURATION SetupConfigurationSelector ReadConfiguration LoadConfigurationFromRegistry Used for all instantiation Or at least for stuff that is more than data containers Registrations made on types not instances At much as possible - not religiously Dependency hints via attributes not strings Ensures refactorbility Prefer constructor injection over property injection For any part we might change: use resolver I.e. Views, Overlays, Dialogs, services (Model, file system, serialization) PRE_BOOT BOOT GET_CONFIGURATION LOAD_CONFIGURATION RUNNING UNLOAD_CONFIGURATION UNBOOT SWITCH_CONFIGURATION FAILURE UNLOAD_CONFIGURATION CloseShell DisposeConfigurationDependentComponentsInOrder [Return to previous state] SWITCH_CONFIGURATION ShowConfigurationSelector [Switch to UNLOAD_CONFIGURATION] [Switch to LOAD_CONFIGURATION] BOOT - configuration agnostic KillOldProcesses SetupLog4net CreateSplashScreen ShowSplashScreen SetupFatalExceptionHandlers SetupVersioningManager SetupPerformanceCounterManager SetupCommandManager SetupThreadingManager SetupCron SetupMessageQueue SetupHttpServer SetupBasicCommands LifeCycle easier to manage through dependency injection Improved unit and integration testing Improved maintainability, composability and more comprehensible Easier to develop new features or replace old views with new ones RUNNING_STATE ExecuteShell MonitorExecution I've identified quite a number of tasks These will be individual classes that can be instantiated and run They are to be configured into specific states FAILURE LogFailureReason [Switch to UNLOAD_CONFIGURATION] [Switch to UNBOOT] RestartApplication PRE_BOOT SpawnThreadForLifeCycle (not a real task) SetupDependencyResolver (not a real task) StartUiThread (not a real task) SetupLifeCycleSystem LoadLifeCycle UNBOOT DisposeBootComponentsInOrder [Return to previous state] Tasks LifeCycle is going well public class Foo { public Foo([Main] IAsyncableThreadInfo mainThread) { ... } } Dependency Injection IDF Client LifeCycle LifeCycle states The resolver itself should only used from the entry point and LifeCycle. In all other places use factories. TypedFactoryFacility supports automatically creating factories from interface. SpawnThreadForLifeCycle (not a real task) SetupDependencyResolver (not a real task) StartUiThread (not a real task) SetupLifeCycleSystem LoadLifeCycle KillOldProcesses SetupLog4net CreateSplashScreen ShowSplashScreen SetupFatalExceptionHandlers SetupVersioningManager SetupPerformanceCounterManager SetupCommandManager SetupThreadingManager SetupCron SetupMessageQueue SetupHttpServer SetupBasicCommands SetupConfigurationSelector ReadConfiguration ShowConfigurationSelector LoadConfigurationFromRegistry SetupLocalizationManager SetupAuthentication SetupModelSupport SetupPurgeManager SetupRestClient ValidateMapiVersion SetupActivityMonitorRestClientAdvisor SetupCommonHeadersRestClientAdvisor SetupSecurityRestClientAdvisor SetupServerTokenValidatingRestClientAdvisor SetupTimeoutRestClientAdvisor SetupKeepAliveRestClientAdvisor SetupDelayOn503ResponseRestClientAdvisor SetupHandleRetrieveNonExistingEntityRestClientAdvisor SetupClientManager SetupListener SetupProxyFactory SetupLocalStorage SetupModel SetupAmbientTransactionManager SetupLazyLoadHelper SetupObservableInterceptor SetupListenerDisallowedObservableInterceptor SetupMarkAsDirtyInterceptor SetupAmbientTransactionInterceptor SetupSwitchTargetInterceptor SetupLazyLoadingInterceptor SetupEventSource SetupEventDispatcher SetupMapiTransactionEventReceiver SetupHeartbeatEventReceiver SetupHttpProxyRequestEventReceiver SetupNetworkStatisticsManager ExecuteShell MonitorExecution CloseShell DisposeConfigurationDependentComponentsInOrder DisposeBootComponentsInOrder LogFailureReason RestartApplication ShowConfigurationSelector

Now you can make any subject more engaging and memorable