1/23/2008This version of Enterprise MSF Agile (with CobiT) is a proof-of-concept that mashes up the lightweight MSF Agile set of practices with a minimal set of governance process elements (Roles, Activities and Work Products) imported from the Acquire and Implement domain of CobiT.
We have chosen CobiT for this mashup as it appeals to an enterprise audience interested in governance. Moreover, CobiT is universally accepted and kept up to date and harmonized with other standards.
Here is a quick overview of what you will get when you create a VSTS team project using this template:
- Work Item Types (WIT): Bug, Risk, Task, Activity, Work Product
- Work Items: 130 instances of Activity WIT, 42 instances of Work Product WIT
- Process Guidance: A link to contextual process guidance from each work item
Having created a VSTS team project using this template your team now has just-in time and just-enough process guidance that incorporates MSF Agile and CobiT best practices and control objectives. Project participants can now work on their everyday tasks guided by process guidance that is "baked" within their environment (integrated ALM framework of VSTS).
Our aim is not provide you with the "full extent of governance" simply because that term is meaningless in the absence of an alignment to your unique business objectives. It has been seen that the most effective way to implement COBIT to achieve governance is by selecting the most appropriate elements, tailoring them as needed and applying them to the specific needs of the organization.
If you are interested in tailoring or mashing up the Enterprise MSF Agile (with CobiT) process for your environment or if you want to have access to second generation enactment capabilities, please contact Osellus and we can set you up with the right tools to get you going. 12/21/2007
The team that came up with MSF for Agile Software Development process suggests choosing it for projects with short lifecycles and delivery-oriented teams who can work without lots of intermediate documentation. MSF for Agile Software Development is an iterative, scenario-driven development process for building .NET, Web, Web Service, and other object-oriented applications. It directly incorporates practices for handling quality of service requirements such as performance and security, utilizes a context-driven approach (context-based) to determine how to operate the project, explicitly calls out project risk as a success criteria for the optimal delivery of software, and incorporates all of the traditional software development roles such as the business analyst, project manager, architect, developer, tester, and release manager. This MSF process is a flexible guidance framework that helps create an adaptive system for software development. This agile methodology anticipates the need to adapt to change, and focuses on people as the most important component to the success of a project. It also emphasizes the delivery of working software and promotes customer validation as key success measures.
Here is a quick overview of what you will get when you create a VSTS team project using this template:
- Work Item Types (WIT): Bug, Risk, Task, Activity, Work Product
- Work Items: 97 instances of Activity WIT, 29 instances of Work Product WIT
- Process Guidance: A link to contextual process guidance from each work item
If you are interested in tailoring or mashing up the MSF for Agile Software Development process for your environment or if you want to have access to second generation enactment capabilities, please contact Osellus and we can set you up with the right tools to get you going. 12/4/2007
This is a subset of 40 control objectives drawn from the Acquire and Implement CobiT domain. By choosing to implement these control objectives, the organization is able to provide a reasonable assurance that the business objectives linked to software development projects will be met.
Here is a quick overview of what you will get when you create a VSTS team project using this template:
- Work Item Types (WIT): Bug, Risk, Task, Activity, Work Product
- Work Items: 33 instances of Activity WIT, 13 instances of Work Product WIT
- Process Guidance: A link to contextual process guidance from each work item
If you are interested in tailoring or mashing up the CobiT_For Software Development Projects process for your environment or if you want to have access to second generation enactment capabilities, please contact Osellus and we can set you up with the right tools to get you going. 11/23/2007
This version of Enterprise OpenUP is a proof-of-concept elevates OpenUP to become suitable for an enterprise audience interested in governance using COBIT, a universally accepted framework that is kept up to date and harmonized with other standards.
OpenUP is an open source development methodology developed under the Eclipse organization. However, amongst other things, it lacks the mechanisms to make it appropriate for use in a serious enterprise implementation. You do have the option to use a comparable commercial tooling such as IBMs Rational Method Composer along with its consulting services in making it governance-ready for your enterprise. But in case you are not prepared to spend a considerable amount of money doing this, here is a way for you to get to low-hanging fruit to move towards implementing a governance framework using this mash-up of OpenUP and COBIT.
In this release of Enterprise OpenUP a subset of COBIT, that could be considered as the minimum needed to start a discussion around governance has been documented. This version in no way claims to provide you with the "full extent of governance" simply because that term is meaningless unless aligned with your unique business objectives. It has been seen that the most effective way to implement COBIT to achieve governance is by selecting the most appropriate elements, tailoring them as needed and applying them to the specific needs of the organization.
In my next release of Enterprise OpenUP (next week) I will detail how the governance concepts, especially RACI have augmented OpenUP to get you closer to achieving your governance objectives.
OpenUP is just the start. Gradually, we will have a mix various non-commercial methodologies such has MSF that can give you a wide base set of processes to choose from. My aim is to lower the barrier to introduce processes within your team. Rather than being limited by the overwhelming steps to come up with your own processes from scratch or to have to pay to get one methodology that you are forced to impose on your teams, IRIS Process Central lets you catch the long tail of processes by (eventually) helping you choose from a list of hundreds of available processes, all tailored for a specific objective. By spending a few hours you can do last-mile tailoring on these processes to make them applicable for your project environment.
This effort requires your input. If you see something that is missing, such as a process or methodology you would like to see in WIKI form or as a VSTS process template or simply want to comment on something you see here please participate in this community. Your feedback will enrich the process community.
Choose the MSF for CMMI Process Improvement process for projects with longer life cycles and that require a record of decisions made. Choose MSF for CMMI Process Improvement over MSF for Agile Software Development, if your organization is undertaking a broad quality assurance and process improvement initiative or your team needs the assistance of explicit process guidance rather than relying on tacit knowledge and experience.
Here is a quick overview of what you will get when you create a VSTS team project using this template:
- Work Item Types (WIT): Bug, Risk, Task, Activity, Work Product
- Work Items: 196 instances of Activity WIT, 58 instances of Work Product WIT
- Process Guidance: A link to contextual process guidance from each work item
If you are interested in tailoring or mashing up the MSF for CMMI Process Improvement process for your environment or if you want to have access to second generation enactment capabilities, please contact Osellus and we can set you up with the right tools to get you going.
The Framework For Business Centered Development (version 4 of DSDM) describes an iterative and incremental approach to developing software that is clearly driven by and responsive to the changing needs of the business. The concept of customer collaboration underpins the DSDM way of working. The iterative DSDM development process is designed specifically to support a number of collaborative techniques to ensure that a project delivers exactly what is needed within the normal constraints of time, budget and resources. The clear definition of a variety of customer roles forms part of DSDM and is considered critical to the success of the approach.
As an Agile process, DSDM promotes active user involvement within the project team and defines specific roles that enable this. The DSDM Plugin for OpenUP adds these roles to the OpenUP base, increasing the team's capability for collaborative software development.
Here is a quick overview of what you will get when you create a VSTS team project using this template:
- Work Item Types (WIT): Activity, Bug, Risk, Task, Work Product
- Work Items: 55 instances of Activity WIT, 19 instances of Work Product WIT
- Process Guidance: A link to contextual process guidance from each work item
If you are interested in tailoring or mashing up the OpenUP DSDM process for your environment or if you want to have access to second generation enactment capabilities, please contact Osellus and we can set you up with the right tools to get you going.
OpenUP is a lean Unified Process that applies iterative and incremental approaches within a structured lifecycle. OpenUP embraces a pragmatic, agile philosophy that focuses on the collaborative nature of software development. It is a tools-agnostic, low-ceremony process that can be extended to address a broad variety of project types.
The OpenUP process template is ready for your use as you create new team projects in Microsoft Visual Studio Team System (VSTS). This process template moves your team to the first step in your ultimate objective of creating a tailored process definition and its flexible process enactment in a evolving team project.
Here is a quick overview of what you will get when you create a VSTS team project using this template:
- Work Item Types (WIT): Activity, Bug, Risk, Task, Work Product
- Work Items: 62 instances of Activity WIT, 18 instances of Work Product WIT
- Process Guidance: A link to contextual process guidance from each work item
If you are interested in tailoring or mashing up the OpenUP process for environment or if you want to have access to second generation enactment capabilities, please contact Osellus and we can set you up with the right tools to get you going. |
|
|
|
|