The document provides an overview of a company with 2 products and over 100 employees organized into many teams and departments. The company uses different processes across its teams and products.
The document describes an organization that has 2 products and over 100 employees divided across many teams and departments. Different processes are used across the teams and departments.
This document describes an organization with 2 products, over 100 employees split across many teams and departments, and different processes. It has a C# team, VB.NET team, core team, integration team, and refactoring team working on .NET refactoring and IDE products.
Given at the BCS in Edinburgh on the 1/8/2012. Talk about change and failed attempt to introduce XP into an organisation. Suggests potential reasons for the failure, introduces Kanban and then speculates as to how change might have been more successful in an evolutionary manner with Kanban.
This document discusses how Kanban can be used to facilitate evolutionary organizational change. It describes Kanban as a change management system that uses visual boards and limits on work-in-progress to provoke incremental, continuous improvement. The document provides examples of how visualizing workflow and restricting work-in-progress can help align teams and processes, overcome resistance to change, and establish a culture of continuous learning.
Blue Monitor Systems is an employee-owned company dedicated to delivering high-quality creative, technical, and scientific services worldwide. The company encourages employees to think like owners and contribute to social well-being. Blue Monitor uses an iterative "Zero Time" method combining Agile and traditional approaches for medium and large projects. This includes continuous integration, test-driven development, and matrix project teams with specialists in design, engineering, testing, and operations.
This document discusses a software generator framework for generative programming. Generative programming aims to deal with software system families by utilizing a generator, implementation components, and a domain-specific configuration language. The presented framework uses Java, Maven and Spring and allows defining features, frames, and content providers to generate customized software products based on an input configuration. It demonstrates how custom logic can be added through a content provider that replaces markers in frame files at generation time.
The document provides instructions for installing and using the Nero Digital plug-in for Adobe Premiere. It allows exporting video projects from Premiere in the Nero Digital (MPEG-4) format. Key steps include setting chapter and subtitle markers in Premiere, exporting to Nero Digital, and configuring video, audio, subtitle and other encoding settings for the Nero Digital profile. Advanced encoding settings can also be customized.
Verteilte SoftwareEntwicklung 2011 - von klassischen Modellen bis Scrum und S...Intland Software GmbH
Präsentation auf der Seacon 2011 in Hamburg.
Neueste Trends in der verteilten Software Entwicklung: Collaboration Tools für EntwicklungsTeams, Einsatz von DVCS
The document describes an organization that has 2 products and over 100 employees divided across many teams and departments. Different processes are used across the teams and departments.
This document describes an organization with 2 products, over 100 employees split across many teams and departments, and different processes. It has a C# team, VB.NET team, core team, integration team, and refactoring team working on .NET refactoring and IDE products.
Given at the BCS in Edinburgh on the 1/8/2012. Talk about change and failed attempt to introduce XP into an organisation. Suggests potential reasons for the failure, introduces Kanban and then speculates as to how change might have been more successful in an evolutionary manner with Kanban.
This document discusses how Kanban can be used to facilitate evolutionary organizational change. It describes Kanban as a change management system that uses visual boards and limits on work-in-progress to provoke incremental, continuous improvement. The document provides examples of how visualizing workflow and restricting work-in-progress can help align teams and processes, overcome resistance to change, and establish a culture of continuous learning.
Blue Monitor Systems is an employee-owned company dedicated to delivering high-quality creative, technical, and scientific services worldwide. The company encourages employees to think like owners and contribute to social well-being. Blue Monitor uses an iterative "Zero Time" method combining Agile and traditional approaches for medium and large projects. This includes continuous integration, test-driven development, and matrix project teams with specialists in design, engineering, testing, and operations.
This document discusses a software generator framework for generative programming. Generative programming aims to deal with software system families by utilizing a generator, implementation components, and a domain-specific configuration language. The presented framework uses Java, Maven and Spring and allows defining features, frames, and content providers to generate customized software products based on an input configuration. It demonstrates how custom logic can be added through a content provider that replaces markers in frame files at generation time.
The document provides instructions for installing and using the Nero Digital plug-in for Adobe Premiere. It allows exporting video projects from Premiere in the Nero Digital (MPEG-4) format. Key steps include setting chapter and subtitle markers in Premiere, exporting to Nero Digital, and configuring video, audio, subtitle and other encoding settings for the Nero Digital profile. Advanced encoding settings can also be customized.
Verteilte SoftwareEntwicklung 2011 - von klassischen Modellen bis Scrum und S...Intland Software GmbH
Präsentation auf der Seacon 2011 in Hamburg.
Neueste Trends in der verteilten Software Entwicklung: Collaboration Tools für EntwicklungsTeams, Einsatz von DVCS
Soccnx III - Using Social Controls in XPagesLetsConnect
Speakers: Martin Donnelly & Tony McGuckin
There is a lot of talk about "social" these days - social applications, social business, social media, social services and so on. This session uses a definition of "social" in the context of IBM Domino XPages, custom application development and IBM Domino/IBM XWork Server. It describes new social requirements, maps them to technologies and shows how the XPages Extension Library helps you create powerful social solutions to integrate with IBM Connections and other social providers within your custom application development. People are connected more than ever, blurring the line between business and private life. For example often employees have Twitter accounts that they use to tweet both private and business messages. Many employees use their private smartphones to access business applications and data. Furthermore, information is scattered more than ever, within enterprises and in public social networks, within on premise systems and on the cloud. The corporate inbox is no longer only the mail inbox, new notifications also come in via IBM Connections, Facebook, Google+, Twitter, LinkedIn, etc! The XPages Extension Library provides utilities that make integration of Social APIs really easy, including a new storage facility for OAuth application and consumer tokens. IBM Domino XPages is on the fast track to help make your applications social. Participate in this session to see the latest contributions to the XPages Extension Library for Social Business. XPages is ready today, are you?
This document discusses the challenges of application delivery in today's environment. It notes that while the cost to run apps is decreasing through virtualization and cloud, the cost to deliver apps remains high due to complexity and compliance issues. This creates a budget squeeze for application development teams. The document proposes that teams can get out of this squeeze by orchestrating their processes to streamline workflows, reduce demand, increase budgets by outsourcing non-critical tasks, trimming application portfolios, and reducing costs. It identifies challenges such as lack of collaboration, distributed teams, manual error-prone processes, and repositories without workflows. It argues that a focus only on artifacts is insufficient and that orchestration is needed for end-to-end trace
Managing variability in software applications - scandev12Stephan Hochdörfer
This document discusses managing variability in software applications. It introduces generative programming as an approach to deal with software system families and reusable components. Generative programming uses a generator to automate the assembly of application implementations from configurable components based on domain-specific product configurations. This increases productivity and quality by reducing complexity and errors compared to point solutions for each customer. The key steps are domain analysis, domain design, domain implementation, and technology projection to implement the generator.
An Agile Architect's major responsibility is to enable continuous delivery of business value by facilitating continuous design, delivery automation, and deployment visibility. This includes practices like test-driven development, automated configuration management, continuous integration, and making the deployment pipeline transparent. The goal is to deliver the right features rapidly through tuned processes, automation, and feedback loops.
- innoWake is a consulting company founded in 2000 that specializes in modernizing legacy applications, with headquarters in Senden, Germany and San Francisco, USA and approximately 50 employees.
- Legacy applications face challenges like increased complexity, shorter development cycles, and higher performance demands. innoWake helps with challenges through development modernization, application modernization, migration, and new development.
- Modernization services include migrating applications to new programming languages, operating systems, and databases to reduce dependencies and costs while maintaining functionality and improving user interfaces.
The document introduces Spring Roo, a tool that aims to make Java development fun by eliminating complexity, boosting productivity, and following principles like KISS and DRY. It discusses problems with traditional Java applications like complexity, lack of DRYness, and boilerplate code. Spring Roo uses simple commands, pragmatic code generation, and aspects to generate basic application structures and address these problems. The core components and development cycle are explained, and examples are provided of entities, controllers, and JSPX views that Roo can automatically generate.
The document introduces Agile software development methods. It discusses the challenges of traditional waterfall methods and outlines Agile values like frequent inspection and adaptation. It then describes the Scrum framework as an example Agile method, including roles, ceremonies, and artifacts. Finally, it provides a case study of how Scrum was successfully adopted by a department at France Telecom.
This document describes IBM Rational software products, including Rational Team Concert for agile development, Rational Requirements Composer for requirements management, Rational DOORS for requirements traceability, Rational Quality Manager for testing, and Rational AppScan for application security testing. It discusses how these products integrate with each other and with Jazz source control through the Jazz Team Server to support collaborative application lifecycle management.
Frameworkevolution ohne Nebenwirkung - Automatische Adaption von Clients und ...SoftwareSaxony
This document discusses two tools, ComeBack! and ADE, for automatically adapting software components when a framework evolves. ComeBack! uses refactoring history to generate adapter layers to preserve binary compatibility between updated frameworks and plugins. ADE uses change mappings specified by developers to guide its adapter generation. The tools aim to reduce costs and improve quality for framework users and maintainers during framework evolution.
The document describes a parking spot locator mobile application that uses image processing of camera images of a parking lot to determine occupied and empty spots, stores this data on a server, and allows a mobile application to access current parking availability information to help users find open spots more quickly. The application was developed over several months and tested successfully, and the document reviews the system components, development process, and plans for marketing and expanding the system.
How to go beyond traditional Scrum principles and scale to globally distributed teams with Continuous Delivery and Subversion. Presented by Andy Singleton of Assembla and Scott Rudenstein of WANdisco. Presented Nov. 15, 2012. 30 minutes.
The document outlines the project workflow for a development team. It details the various stages of development from design to testing to deployment. Key aspects include using git flow for source control, tracking stories and tasks in Pivotal Tracker, continuous integration with each build generating reports, beta releases for testing, and integrating live data into the production system. Feedback from beta testing is also gathered to identify bugs and potential improvements.
This document discusses techniques for continuous integration and deployment using Hudson. It recommends using Hudson to automate the build, testing and deployment process. This allows for faster feedback, better visibility and automated delivery. It describes how to use various Hudson plugins to implement continuous integration practices like automatic builds, testing, code quality metrics, notifications and promoting builds through test, UAT and production environments. The goal is to deploy code changes into production automatically through a continuous deployment pipeline.
This document discusses how agile development teams can use IBM Rational ClearCase and ClearCase Remote Client (CCRC) for software configuration management. It covers ClearCase object topologies and practices that support agile development, as well as CCRC features that help enable agile practices like continuous integration and working in a distributed environment. The presentation focuses on how ClearCase can be implemented simply to support agile teams while also scaling to meet the needs of large enterprises.
Agile methods are based on short iterations delivering functionality in increments, with small, well-defined work requests consisting of just enough requirements definition at just the right time. But with such a short-term focus, how can agile teams manage a product portfolio over months or even years? We'll talk about the building blocks of an effective agile portfolio management strategy, starting with the core tools of the Product Owner, and extending these to look beyond the next few weeks of work into planning and tracking a product release or portfolio over several months.
The document describes an organization that has 2 products and over 100 employees divided across many teams and departments. Different processes are used across the teams and departments.
The document describes a company that has two products and over 100 employees divided across many teams and departments. It includes wireframes for tracking progress of user stories and bugs across multiple projects and teams in TargetProcess planning tool. The wireframes show features for selecting scope, viewing team progress burndowns, getting details of work items, and dragging work items between backlog and sprint boards.
The Web Development Eco-system with VSTS, ASP.NET 2.0 & Microsoft AjaxDarren Sim
This document provides an overview of the Visual Studio Team System (VSTS) for web development. It discusses common pains experienced by web development teams and how VSTS addresses them through integrated tools for source control, work item tracking, reporting, build automation, and project portals. Key features of VSTS demonstrated include change management, work item management, shared and exclusive checkouts, promotion modeling, and reports. Additional resources for learning more about VSTS are also provided.
The document discusses strategies for continuous delivery through parallel development and continuous integration, including maintaining feature branches, release branches, and a main development branch. It also outlines the general development workflow and processes for building, deploying, acceptance testing, releasing, and pushing updates to production through automated deployment. The goal is to enable one-click software updates and releases at any time through establishing testing, integration, and deployment best practices.
Blue Monitor Systems Software Development Servicesbluemonitor
Blue Monitor Systems is an employee-owned company dedicated to delivering high-quality creative, technical, and scientific services worldwide. The company encourages employees to think like owners and contribute to social good in the communities where they operate. Blue Monitor uses an iterative "Zero Time" development method combining Agile and traditional approaches. This allows for monthly major releases across multiple projects through a matrix team structure and well-defined engineering processes.
Soccnx III - Using Social Controls in XPagesLetsConnect
Speakers: Martin Donnelly & Tony McGuckin
There is a lot of talk about "social" these days - social applications, social business, social media, social services and so on. This session uses a definition of "social" in the context of IBM Domino XPages, custom application development and IBM Domino/IBM XWork Server. It describes new social requirements, maps them to technologies and shows how the XPages Extension Library helps you create powerful social solutions to integrate with IBM Connections and other social providers within your custom application development. People are connected more than ever, blurring the line between business and private life. For example often employees have Twitter accounts that they use to tweet both private and business messages. Many employees use their private smartphones to access business applications and data. Furthermore, information is scattered more than ever, within enterprises and in public social networks, within on premise systems and on the cloud. The corporate inbox is no longer only the mail inbox, new notifications also come in via IBM Connections, Facebook, Google+, Twitter, LinkedIn, etc! The XPages Extension Library provides utilities that make integration of Social APIs really easy, including a new storage facility for OAuth application and consumer tokens. IBM Domino XPages is on the fast track to help make your applications social. Participate in this session to see the latest contributions to the XPages Extension Library for Social Business. XPages is ready today, are you?
This document discusses the challenges of application delivery in today's environment. It notes that while the cost to run apps is decreasing through virtualization and cloud, the cost to deliver apps remains high due to complexity and compliance issues. This creates a budget squeeze for application development teams. The document proposes that teams can get out of this squeeze by orchestrating their processes to streamline workflows, reduce demand, increase budgets by outsourcing non-critical tasks, trimming application portfolios, and reducing costs. It identifies challenges such as lack of collaboration, distributed teams, manual error-prone processes, and repositories without workflows. It argues that a focus only on artifacts is insufficient and that orchestration is needed for end-to-end trace
Managing variability in software applications - scandev12Stephan Hochdörfer
This document discusses managing variability in software applications. It introduces generative programming as an approach to deal with software system families and reusable components. Generative programming uses a generator to automate the assembly of application implementations from configurable components based on domain-specific product configurations. This increases productivity and quality by reducing complexity and errors compared to point solutions for each customer. The key steps are domain analysis, domain design, domain implementation, and technology projection to implement the generator.
An Agile Architect's major responsibility is to enable continuous delivery of business value by facilitating continuous design, delivery automation, and deployment visibility. This includes practices like test-driven development, automated configuration management, continuous integration, and making the deployment pipeline transparent. The goal is to deliver the right features rapidly through tuned processes, automation, and feedback loops.
- innoWake is a consulting company founded in 2000 that specializes in modernizing legacy applications, with headquarters in Senden, Germany and San Francisco, USA and approximately 50 employees.
- Legacy applications face challenges like increased complexity, shorter development cycles, and higher performance demands. innoWake helps with challenges through development modernization, application modernization, migration, and new development.
- Modernization services include migrating applications to new programming languages, operating systems, and databases to reduce dependencies and costs while maintaining functionality and improving user interfaces.
The document introduces Spring Roo, a tool that aims to make Java development fun by eliminating complexity, boosting productivity, and following principles like KISS and DRY. It discusses problems with traditional Java applications like complexity, lack of DRYness, and boilerplate code. Spring Roo uses simple commands, pragmatic code generation, and aspects to generate basic application structures and address these problems. The core components and development cycle are explained, and examples are provided of entities, controllers, and JSPX views that Roo can automatically generate.
The document introduces Agile software development methods. It discusses the challenges of traditional waterfall methods and outlines Agile values like frequent inspection and adaptation. It then describes the Scrum framework as an example Agile method, including roles, ceremonies, and artifacts. Finally, it provides a case study of how Scrum was successfully adopted by a department at France Telecom.
This document describes IBM Rational software products, including Rational Team Concert for agile development, Rational Requirements Composer for requirements management, Rational DOORS for requirements traceability, Rational Quality Manager for testing, and Rational AppScan for application security testing. It discusses how these products integrate with each other and with Jazz source control through the Jazz Team Server to support collaborative application lifecycle management.
Frameworkevolution ohne Nebenwirkung - Automatische Adaption von Clients und ...SoftwareSaxony
This document discusses two tools, ComeBack! and ADE, for automatically adapting software components when a framework evolves. ComeBack! uses refactoring history to generate adapter layers to preserve binary compatibility between updated frameworks and plugins. ADE uses change mappings specified by developers to guide its adapter generation. The tools aim to reduce costs and improve quality for framework users and maintainers during framework evolution.
The document describes a parking spot locator mobile application that uses image processing of camera images of a parking lot to determine occupied and empty spots, stores this data on a server, and allows a mobile application to access current parking availability information to help users find open spots more quickly. The application was developed over several months and tested successfully, and the document reviews the system components, development process, and plans for marketing and expanding the system.
How to go beyond traditional Scrum principles and scale to globally distributed teams with Continuous Delivery and Subversion. Presented by Andy Singleton of Assembla and Scott Rudenstein of WANdisco. Presented Nov. 15, 2012. 30 minutes.
The document outlines the project workflow for a development team. It details the various stages of development from design to testing to deployment. Key aspects include using git flow for source control, tracking stories and tasks in Pivotal Tracker, continuous integration with each build generating reports, beta releases for testing, and integrating live data into the production system. Feedback from beta testing is also gathered to identify bugs and potential improvements.
This document discusses techniques for continuous integration and deployment using Hudson. It recommends using Hudson to automate the build, testing and deployment process. This allows for faster feedback, better visibility and automated delivery. It describes how to use various Hudson plugins to implement continuous integration practices like automatic builds, testing, code quality metrics, notifications and promoting builds through test, UAT and production environments. The goal is to deploy code changes into production automatically through a continuous deployment pipeline.
This document discusses how agile development teams can use IBM Rational ClearCase and ClearCase Remote Client (CCRC) for software configuration management. It covers ClearCase object topologies and practices that support agile development, as well as CCRC features that help enable agile practices like continuous integration and working in a distributed environment. The presentation focuses on how ClearCase can be implemented simply to support agile teams while also scaling to meet the needs of large enterprises.
Agile methods are based on short iterations delivering functionality in increments, with small, well-defined work requests consisting of just enough requirements definition at just the right time. But with such a short-term focus, how can agile teams manage a product portfolio over months or even years? We'll talk about the building blocks of an effective agile portfolio management strategy, starting with the core tools of the Product Owner, and extending these to look beyond the next few weeks of work into planning and tracking a product release or portfolio over several months.
The document describes an organization that has 2 products and over 100 employees divided across many teams and departments. Different processes are used across the teams and departments.
The document describes a company that has two products and over 100 employees divided across many teams and departments. It includes wireframes for tracking progress of user stories and bugs across multiple projects and teams in TargetProcess planning tool. The wireframes show features for selecting scope, viewing team progress burndowns, getting details of work items, and dragging work items between backlog and sprint boards.
The Web Development Eco-system with VSTS, ASP.NET 2.0 & Microsoft AjaxDarren Sim
This document provides an overview of the Visual Studio Team System (VSTS) for web development. It discusses common pains experienced by web development teams and how VSTS addresses them through integrated tools for source control, work item tracking, reporting, build automation, and project portals. Key features of VSTS demonstrated include change management, work item management, shared and exclusive checkouts, promotion modeling, and reports. Additional resources for learning more about VSTS are also provided.
The document discusses strategies for continuous delivery through parallel development and continuous integration, including maintaining feature branches, release branches, and a main development branch. It also outlines the general development workflow and processes for building, deploying, acceptance testing, releasing, and pushing updates to production through automated deployment. The goal is to enable one-click software updates and releases at any time through establishing testing, integration, and deployment best practices.
Blue Monitor Systems Software Development Servicesbluemonitor
Blue Monitor Systems is an employee-owned company dedicated to delivering high-quality creative, technical, and scientific services worldwide. The company encourages employees to think like owners and contribute to social good in the communities where they operate. Blue Monitor uses an iterative "Zero Time" development method combining Agile and traditional approaches. This allows for monthly major releases across multiple projects through a matrix team structure and well-defined engineering processes.
CI (continuous integration) is fundamental for agile deployment and should be improved step-by-step. Issue tracking tools like JIRA, Redmine, and spreadsheets can manage requirements and tasks. Code review is an important part of the coding process and helps improve code quality and mentorship. Distributed version control systems like Git provide more flexible workflows than centralized ones and integrate well with code review tools like Gerrit.
This document provides an overview of a tutorial on Java development using Rational Application Developer. The tutorial teaches how to create Java projects and packages, and develop Java classes using features like the Java editor, content assist, and code generation. It describes perspectives and views in the IDE and how to set up a development environment for Java. The overall goal is to help prepare developers for an IBM certification exam on Java development.
The document discusses new features in Lotus Notes 8.5.1 and Expeditor 6.2.1 that simplify building composite applications without programming. It highlights ready-to-use component templates for rapidly transforming existing applications into composite applications. The key new features include simple containers for building components, declarative assembly using XML, and component-to-component communication through a property broker.
1. Ext Designer is a UI builder for Ext JS that allows rapidly arranging and configuring Ext JS components visually. It generates first-class Ext JS components that can be exported and used in an IDE or browser.
2. The Designer workflow involves creating and configuring components and data stores, exporting to disk, importing into an IDE, and implementing business logic and behavior.
3. Advanced configuration techniques in Designer include function-type component configurations, adding plugins, and integrating user extensions, while still leveraging the visual design capabilities of Designer.
Continuous Delivery refers to the process of releasing high quality software quickly and with confidence through the use of build, test and deployment automation. By applying Lean techniques to the development, test and deployment of software, waste is reduced and staff are freed up to work on more important tasks. By following a continuous delivery model, release cycles shift from a matter of months to weeks or days.
In this presentation, we will look at the key tools and processes involved in transitioning from a manual culture to one that embraces automation. We will look at real world examples, including the tools and architectural components. We will discuss organizational impacts, including the dramatic improvements in morale as team delivery commitments are met more easily through automation.
Heterogeneous Development With RTC - Sreerupa SenRoopa Nadkarni
This document provides an overview of Rational Team Concert for Microsoft Visual Studio IDE. It discusses key features like source control integration, work item tracking, builds, and planning integration directly within Visual Studio. It also covers how the product enables heterogeneous teams with a common Jazz platform and provides a similar experience across IDEs through its Eclipse and Visual Studio clients. Self-hosting practices helped shape the product to better meet the needs of Visual Studio developers.
Att lyckas med integration av arbetet från flera scrum team - Christophe Acho...manssandstrom
This document discusses strategies for integrating work from multiple Scrum teams. It outlines the role of an integration team in continuously integrating work. Key success factors for the integration team include: integrating work early, having the necessary resources and environments, practicing continuous integration, using automated tests, maintaining at least two test environments, performing early performance tests, stopping work if integration breaks, having a clear contract between development and integration teams, making the integration process and status visible.
The document summarizes new features and improvements for GitLab version 9.0.5 and 9.1, including navigation improvements, new documentation topics, comparisons to other tools, improved index pages, and the completion of version 9.1. It also outlines new features for GitLab Enterprise Edition, such as a Service Desk for customer support, Canary deploys to test releases, burndown charts to track milestone progress, improved template access, and linking between project pipeline views. The document asks if there are any questions.
The document compares the architecture of Cognos 8.2, OBIEE 10g, and OBIEE 11g across several features. Some key differences include:
- OBIEE 10g and 11g are based on N-tier architectures while Cognos uses a web-based service-oriented architecture.
- OBIEE 10g and 11g require desktop tools for repository development and management while Cognos 8.2 is platform independent.
- OBIEE 11g improved support for clustering, load balancing, and in-memory capabilities compared to earlier versions.
- All three support integration with external applications, single sign-on, and LDAP integration for security. However,
The document discusses the release of the .NET SDK and Visual Studio plug-in for the Intel AppUp developer program, which provides tools for .NET developers to easily create and sell applications for Intel Atom-powered devices. The .NET SDK includes methods for authorization, instrumentation, and crash reporting. It can be implemented within minutes. The plug-in allows developers to perform submission tasks from within Visual Studio. This release opens new opportunities for .NET developers and makes it easy to port existing .NET applications to the AppUp marketplace.
The document discusses the release of the .NET SDK and Visual Studio plug-in for the Intel AppUp developer program, which provides tools for .NET developers to easily create and sell applications for Intel Atom-powered devices. The .NET SDK includes methods for authorization, instrumentation, and crash reporting. It can be implemented within minutes. The plug-in allows developers to perform submission tasks from within Visual Studio. This release opens new opportunities for .NET developers and makes it easy to port existing .NET applications to the AppUp marketplace.
Visual Basic 9.0 Trucs Et Astuces Dans Visual Studio 2008Gregory Renard
The document discusses new features and improvements in Visual Studio 2008 and Visual Basic 9.0. It covers areas like customization, operator overloading, code snippets, macros, the debugger, LINQ, generics, Windows and web applications, refactoring, and more. It also provides links to Microsoft blogs and sites for additional Visual Basic and Visual Studio resources and support.
Visual Basic 9.0 Trucs Et Astuces Dans Visual Studio 2008Gregory Renard
The document discusses new features and improvements in Visual Studio 2008 and Visual Basic 9.0. It covers areas like customization, operator overloading, code snippets, macros, the debugger, LINQ, generics, Windows and web applications, refactoring, and more. It also provides links to Microsoft blogs and websites for additional resources on Visual Basic development.
Visual Basic 9.0 Trucs Et Astuces Dans Visual Studio 2008
Planning with timeline
1. Has 2 products. Has 100+ people. Has many teams and departments. Different processes are used
.NET Refactoring Product
works for all projects in product
C# Refactoring
C# Team
works only for VB.NET VB.NET Refactoring
VB.NET Team
works for whole product
IDE Product
Core Team works for whole product
Core
Plugins
Integration Team
Refactoring Tool
RefactoringTeam
2. The wireframes in this package are related to planning with timeline
for multi projects and multi teams
It is strongly recommended to view slides in order of their appearance
3. Logo
Planning with timeline
All Projects
Navigation Panel
Features, stories and bugs stories, bugs and features for .NET Refactoring and IDE products. Change this scope
in backlog Need more details?
- Select Project
May Jun Jul
keyword... Projects Teams
today
Stories Bugs Features
C# Refactoring Release 2.1 Release 2.2
214 Create some 145 Fix some
feature issue
214 Create some 145 Fix some
feature issue
Release 1.9 Support and bug fixing
214 Create some 214 Create some
feature feature
214 Create some 145 Fix some
feature issue
Release 2.1 Release 2.2
214 Create some 145 Fix some VB.NET
feature issue
Refactoring
214 Create some 145 Fix some
feature issue
Release 2.1
214 Create some 145 Fix some
feature issue Release 6.2
Core
Release 6.1.1 Support and bug fixing
4. Logo
Planning with timeline
All Projects
You can scroll the timeline to the right to plan
Navigation Panel
feature releases
Features, stories and bugs stories, bugs and features for .NET Refactoring and IDE products. Change this scope
in backlog Need more details?
- Select Project
May Jun Jul
keyword... Projects Teams
today
Stories Bugs Features
C# Refactoring Release 2.1 Release 2.2
214 Create some 145 Fix some
feature issue
214 Create some 145 Fix some
feature issue
Release 1.9 Support and bug fixing
214 Create some 214 Create some
feature feature
214 Create some 145 Fix some
feature issue
Release 2.1 Release 2.2
214 Create some 145 Fix some VB.NET
feature issue
Refactoring
214 Create some 145 Fix some
feature issue
Release 2.1
214 Create some 145 Fix some
feature issue Release 6.2
Core
Release 6.1.1 Support and bug fixing
5. Logo
Planning with timeline
All Projects
Navigation Panel
Features, stories and bugs stories, bugs and features for .NET Refactoring and IDE products. Change this scope
in backlog Need more details? Current release is highlighted with green
- Select Project
May Jun Jul
keyword... Projects Teams
today
Stories Bugs Features
C# Refactoring Release 2.1 Release 2.2
214 Create some 145 Fix some
feature issue
214 Create some 145 Fix some
feature issue
Release 1.9 Support and bug fixing
214 Create some 214 Create some
feature feature
214 Create some 145 Fix some
feature issue
Release 2.1 Release 2.2
214 Create some 145 Fix some VB.NET
feature issue
Refactoring
214 Create some 145 Fix some
feature issue
Release 2.1
214 Create some 145 Fix some
feature issue Release 6.2
Core
Release 6.1.1 Support and bug fixing
6. Logo
Planning with timeline
All Projects
Navigation Panel
Features, stories and bugs stories, bugs and features for .NET Refactoring and IDE products. Change this scope
in backlog Need more details?
- Select Project
May Jun Jul
keyword... Projects Teams
today
Stories Bugs Features
You can assign entity to the release
C# Refactoring Release 2.1 Release 2.2
214 Create some 145 Fix some
feature issue
214 Create some 145 Fix some
feature issue
214 Create some Release 1.9 Support and bug fixing
214 Create some 214 Create some feature
feature feature
214 Create some 145 Fix some
feature issue
Release 2.1 Release 2.2
214 Create some 145 Fix some VB.NET
feature issue
Refactoring
214 Create some 145 Fix some
feature issue
Release 2.1
214 Create some 145 Fix some
feature issue Release 6.2
Core
Release 6.1.1 Support and bug fixing
7. Logo
Planning with timeline
All Projects
Navigation Panelcan show more details by dragging slider
You
to the right
Features, stories and bugs stories, bugs and features for .NET Refactoring and IDE products. Change this scope
in backlog Need more details?
- Select Project
May Jun Jul
keyword... Projects Teams
today
Stories Bugs Features
C# Refactoring Release 2.1 Release 2.2
214 Create some 145 Fix some
feature issue
214 Create some 145 Fix some
feature issue
Release 1.9 Support and bug fixing
214 Create some 214 Create some
feature feature
214 Create some 145 Fix some
feature issue
Release 2.1 Release 2.2
214 Create some 145 Fix some VB.NET
feature issue
Refactoring
214 Create some 145 Fix some
feature issue
Release 2.1
214 Create some 145 Fix some
feature issue Release 6.2
Core
Release 6.1.1 Support and bug fixing
8. Logo
Planning with timeline
All Projects
Navigation Panel
Features, stories and bugs stories, bugs and features for .NET Refactoring and IDE products. Change this scope
in backlog Need more details?
- Select Project
May Jun Jul
keyword... Projects Teams
today
The green shapes show features
Stories Bugs Features assigned to release. Feature contains user
C# Refactoring Release 2.1
stories assigned to it.
Release 2.2
214 Create some 145 Fix some
feature issue
214 Create some 145 Fix some
feature issue
Release 1.9 Support and bug fixing
214 Create some 214 Create some
feature feature
214 Create some 145 Fix some
feature issue
Release 2.1 Release 2.2
214 Create some 145 Fix some VB.NET
feature issue
Refactoring
214 Create some 145 Fix some
feature issue
Release 2.1
214 Create some 145 Fix some
feature issue Release 6.2
Core
Release 6.1.1 Support and bug fixing
9. Logo
Planning with timeline
All Projects
Navigation Panel
Features, stories and bugs stories, bugs and features for .NET Refactoring and IDE products. Change this scope
in backlog Need more details?
- Select Project
May Jun Jul
keyword... Projects Teams
today
Stories Bugs Features
C# Refactoring Release 2.1 Release 2.2
214 Create some 145 Fix some
feature issue
214 Create some 145 Fix some
feature issue
Release 1.9 Support and bug fixing
214 Create some 214 Create some
feature feature
It is cross-project release
214 Create some 145 Fix some
feature issue
Release 2.1 Release 2.2
214 Create some 145 Fix some VB.NET
feature issue
Refactoring
214 Create some 145 Fix some
feature issue
Release 2.1
214 Create some 145 Fix some
feature issue Release 6.2
Core
Release 6.1.1 Support and bug fixing
10. Logo
Planning with timeline
All Projects
Navigation Panel
Features, stories and bugs stories, bugs and features for .NET Refactoring and IDE products. Change this scope
in backlog Need more details?
- Select Project
May Jun Jul
keyword... Projects Teams
today
Stories Bugs Features
C# Refactoring Release 2.1 Release 2.2
214 Create some 145 Fix some
feature issue
214 Create some 145 Fix some
feature issue
Release 1.9 Support and bug fixing
214 Create some 214 Create some
feature feature
214 Create some 145 Fix some
feature issue
You can zoom the release. The magnifier tool
Release 2.1 is shown when mouse over the release.
Release 2.2
214 Create some 145 Fix some VB.NET
feature issue
Refactoring Let's ZOOM it.
214 Create some 145 Fix some
feature issue
Release 2.1
214 Create some 145 Fix some
feature issue Release 6.2
Core
Release 6.1.1 Support and bug fixing
11. Logo
Planning with timeline
All Projects
Navigation Panel
stories, bugs and features in Release 2.1 for .NET Refactoring and IDE products. Change this scope
Features, stories and bugs
in backlog Need more details?
- Select Project today
May
2 8 10 11 13 15 18 22
keyword... Projects Teams 1 3 4 5 6 7 9 12 14 16 17 19 20 21
Stories Bugs Features
C# Refactoring Sprint 2.1.1 Sprint 2.1.2
214 Create some 145 Fix some
feature issue
214 Create some 145 Fix some
feature issue
Sprint 2.1.3 Support
214 Create some 214 Create some
feature feature
214 Create some 145 Fix some
feature issue
Sprint 2.1.1 Sprint 2.1.2
214 Create some 145 Fix some
VB.NET
feature issue
Refactoring
214 Create some 145 Fix some
feature issue
214 Create some 145 Fix some
feature issue
Core
Sprint 2.1.1 Core Sprint 2.1.2 Core
12. Logo
Planning with timeline
All Projects
Navigation Panel
stories, bugs and features in Release 2.1 for .NET Refactoring and IDE products. Change this scope
Features, stories and bugs
in backlog Need more details?
- Select Project today
May
2 8 10 11 13 15 18 22
keyword... Projects Teams 1 3 4 5 6 7 9 12 14 16 17 19 20 21
Stories Bugs Features
C# Refactoring Sprint 2.1.1 Sprint 2.1.2
214 Create some 145 Fix some
feature issue
214 Create some 145 Fix some
feature issue
Sprint 2.1.3 Support
214 Create some 214 Create some
feature feature it is cross-project sprint
214 Create some 145 Fix some
feature issue
Sprint 2.1.1 Sprint 2.1.2
214 Create some 145 Fix some
VB.NET
feature issue
Refactoring
214 Create some 145 Fix some
feature issue
214 Create some 145 Fix some
feature issue
Core
Sprint 2.1.1 Core Sprint 2.1.2 Core
13. Logo
Planning with timeline
All Projects
Navigation Panel
stories, bugs and features in Release 2.1 for .NET Refactoring and IDE products. Change this scope
Features, stories and bugs
in backlog Need more details?
- Select Project today
May
2 8 10 11 13 15 18 22
keyword... Projects Teams 1 3 4 5 6 7 9 12 14 16 17 19 20 21
Stories Bugs Features
C# Refactoring Sprint 2.1.1 Sprint 2.1.2
214 Create some 145 Fix some
feature issue
214 Create some 145 Fix some
feature issue
Sprint 2.1.3 Support
214 Create some 214 Create some
feature feature
214 Create some 145 Fix some
feature issue You can increase/decrease duration
and change start/end dates of sprint
Sprint 2.1.1 Sprint 2.1.2
using drag (mouse near the border)
214 Create some 145 Fix some
VB.NET
feature issue
Refactoring
214 Create some 145 Fix some
feature issue
214 Create some 145 Fix some
feature issue
Core
Sprint 2.1.1 Core Sprint 2.1.2 Core
14. Logo
Planning with timeline
All Projects
Navigation Panel
Let's get more details on this view
stories, bugs and features in Release 2.1 for .NET Refactoring and IDE products. Change this scope
Features, stories and bugs
in backlog Need more details?
- Select Project today
May
2 8 10 11 13 15 18 22
keyword... Projects Teams 1 3 4 5 6 7 9 12 14 16 17 19 20 21
Stories Bugs Features
C# Refactoring Sprint 2.1.1 Sprint 2.1.2
214 Create some 145 Fix some
feature issue
214 Create some 145 Fix some
feature issue
Sprint 2.1.3 Support
214 Create some 214 Create some
feature feature
214 Create some 145 Fix some
feature issue
Sprint 2.1.1 Sprint 2.1.2
214 Create some 145 Fix some
VB.NET
feature issue
Refactoring
214 Create some 145 Fix some
feature issue
214 Create some 145 Fix some
feature issue
Core
Sprint 2.1.1 Core Sprint 2.1.2 Core
15. Logo
Planning with timeline
All Projects
Navigation Panel
stories, bugs and features in Release 2.1 for .NET Refactoring and IDE products. Change this scope
Features, stories and bugs
in backlog Need more details?
- Select Project today
May 2 8 10 11 13
keyword... Projects Teams 1 3 4 5 6 7 9 12 14
Stories Bugs Features
C# Refactoring
214 Create some 145 Fix some Sprint 2.1.1
feature issue
214 Create some 214 Create some 214 Create some 214 Create some 214 Create some 145 Fix some
feature feature feature feature feature issue
214 Create some 145 Fix some
feature issue
214 Create some 214 Create some 214 Create some 214 Create some 214 Create some 214 Create some
feature feature feature feature feature feature
214 Create some 214 Create some
feature feature
214 Create some 214 Create some 214 Create some 214 Create some 214 Create some 214 Create some
214 Create some 145 Fix some feature feature feature feature feature feature
feature issue
214 Create some 145 Fix some 214 Create some 214 Create some 214 Create some 214 Create some 214 Create some 214 Create some
feature issue feature feature feature feature feature feature
214 Create some 145 Fix some
214 Create some 214 Create some 214 Create some 214 Create some 214 Create some 214 Create some
feature issue
feature feature feature feature feature feature
214 Create some 145 Fix some
feature issue
Sprint 2.1.3 Support
145 Fix some 145 Fix some 14
issue issue
16. Logo
Planning with timeline
All Projects
Navigation Panel
stories, bugs and features in Release 2.1 for .NET Refactoring and IDE products. Change this scope
Features, stories and bugs
in backlog Need more details?
- Select Project today
May 2 8 10 11 13
keyword... Projects Teams 1 3 4 5 6 7 9 12 14
Stories Bugs Features
C# Refactoring
214 Create some 145 Fix some Sprint 2.1.1
feature issue
214 Create some 214 Create some 214 Create some 214 Create some 214 Create some 145 Fix some
feature feature feature feature feature issue
214 Create some 145 Fix some
feature issue
214 Create some 214 Create some 214 Create some 214 Create some 214 Create some 214 Create some
feature feature feature feature feature feature
214 Create some 214 Create some
feature feature
214 Create some 214 Create some 214 Create some 214 Create some 214 Create some 214 Create some
214 Create some 145 Fix some feature feature feature feature feature feature
feature issue
214 Create some 145 Fix some 214 Create some 214 Create some 214 Create some 214 Create some 214 Create some 214 Create some
feature issue feature feature feature feature feature feature
You can scroll to look in details for other
sprints
214 Create some 145 Fix some
214 Create some 214 Create some 214 Create some 214 Create some 214 Create some 214 Create some
feature issue
feature feature feature feature feature feature
214 Create some 145 Fix some
feature issue
Sprint 2.1.3 Support
145 Fix some 145 Fix some 14
issue issue
17. Logo
Planning with timeline
All Projects
Navigation Panel
stories, bugs and features in Release 2.1 for .NET Refactoring and IDE products. Change this scope
Features, stories and bugs
in backlog Need more details?
- Select Project today
May 2 8 10 11 13
keyword... Projects Teams 1 3 4 5 6 7 9 12 14
Stories Bugs Features
C# Refactoring
214 Create some 145 Fix some Sprint 2.1.1
feature issue
214 Create some
feature
You can assign entity Create some
214 Create some
feature
214
to the sprint
feature
214 Create some
feature
214 Create some
feature
145 Fix some
issue
214 Create some 145 Fix some
feature issue
214 Create some 214 Create some 214 Create some 214 Create some 214 Create some 214 Create some
feature feature feature feature feature feature
214 Create some 214 Create some
feature feature
214 Create some 214 Create some 214 Create some 214 Create some 214 Create some 214 Create some
214 Create some 145 Fix some 214 Create some feature feature feature feature feature feature
feature issue feature
214 Create some 145 Fix some 214 Create some 214 Create some 214 Create some 214 Create some 214 Create some 214 Create some
feature issue feature feature feature feature feature feature
214 Create some 145 Fix some
214 Create some 214 Create some 214 Create some 214 Create some 214 Create some 214 Create some
feature issue
feature feature feature feature feature feature
214 Create some 145 Fix some
feature issue
Sprint 2.1.3 Support
145 Fix some 145 Fix some 14
issue issue
18. Logo
Planning with timeline
All Projects
Navigation Panel
stories, bugs and features in Release 2.1 for .NET Refactoring and IDE products. Change this scope
Features, stories and bugs
in backlog Need more details?
- Select Project today
May 2 8 10 11 13
keyword... Projects Teams 1 3 4 5 6 7 9 12 14
Stories Bugs Features
C# Refactoring
You can move entity to another sprint
214 Create some 145 Fix some Sprint 2.1.1
feature issue
214 Create some 214 Create some 214 Create some 214 Create some 214 Create some 145 Fix some
feature feature feature feature feature issue
214 Create some 145 Fix some
feature issue
214 Create some 214 Create some 214 Create some 214 Create some 214 Create some 214 Create some
feature feature feature feature feature feature
214 Create some 214 Create some
feature feature
214 Create some 214 Create some 214 Create some 214 Create some 214 Create some 214 Create some
214 Create some 145 Fix some feature feature feature feature feature feature
feature issue 214 Create some
feature
214 Create some 145 Fix some 214 Create some 214 Create some 214 Create some 214 Create some 214 Create some 214 Create some
feature issue feature feature feature feature feature feature
214 Create some 145 Fix some
214 Create some 214 Create some 214 Create some 214 Create some 214 Create some 214 Create some
feature issue
feature feature feature feature feature feature
214 Create some 145 Fix some
feature issue
Sprint 2.1.3 Support
145 Fix some 145 Fix some 14
issue issue
19. Logo
Planning with timeline
All Projects
Navigation Panel
stories, bugs and features in Release 2.1 for .NET Refactoring and IDE products. Change this scope
Features, stories and bugs
in backlog Need more details?
- Select Project today
May 2 8 10 11 13
keyword... Projects Teams 1 3 4 5 6 7 9 12 14
Stories Bugs Features
C# Refactoring
214 Create some 145 Fix some Sprint 2.1.1
feature issue
214 Create some 214 Create some 214 Create some 214 Create some 214 Create some 145 Fix some
feature feature feature feature feature issue
214 Create some 145 Fix some
feature issue
214 Create some 214 Create some 214 Create some 214 Create some 214 Create some 214 Create some
feature feature feature feature feature feature
214 Create some 214 Create some 214 Create some
feature feature feature
214 Create some 214 Create some 214 Create some 214 Create some 214 Create some 214 Create some
214 Create some 145 Fix some feature feature feature feature feature feature
feature issue
214 Create some 145 Fix some 214 Create some 214 Create some 214 Create some 214 Create some 214 Create some 214 Create some
feature issue You can prioritize inside sprint
feature feature feature feature feature feature
214 Create some 145 Fix some
214 Create some 214 Create some 214 Create some 214 Create some 214 Create some 214 Create some
feature issue
feature feature feature feature feature feature
214 Create some 145 Fix some
feature issue
Sprint 2.1.3 Support
145 Fix some 145 Fix some 14
issue issue
20. Logo
Planning with timeline
All Projects
Navigation Panel
stories, bugs and features in Release 2.1 for .NET Refactoring and IDE products. Change this scope
Features, stories and bugs
in backlog Need more details?
- Select Project today
May 2 8 10 11 13
keyword... Projects Teams 1 3 4 5 6 7 9 12 14
Stories Bugs Features
C# Refactoring
214 Create some 145 Fix some Sprint 2.1.1
feature issue
214 Create some 214 Create some 214 Create some 214 Create some 214 Create some 145 Fix some
feature feature feature feature feature issue
214 Create some 145 Fix some
feature issue
214 Create some 214 Create some 214 Create some 214 Create some 214 Create some 214 Create some
feature feature feature feature feature feature
214 Create some 214 Create some
feature feature
214 Create some 214 Create some 214 Create some 214 Create some 214 Create some 214 Create some
214 Create some 145 Fix some feature feature feature feature feature feature
feature issue
214 Create some 145 Fix some 214 Create some 214 Create some 214 Create some 214 Create some 214 Create some 214 Create some
feature issue feature feature feature feature feature feature
214 Create some 145 Fix some
214 Create some 214 Create some You Createzoom team Create sprint. The Create some
214 can some 214 and some 214 214 Create some
feature issue
feature feature behavior is the same all the way feature
feature feature feature
214 Create some 145 Fix some
feature issue
Sprint 2.1.3 Support
145 Fix some 145 Fix some 14
issue issue