• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Scrum And Sepg
 

Scrum And Sepg

on

  • 2,553 views

scrum sepg

scrum sepg

Statistics

Views

Total Views
2,553
Views on SlideShare
2,550
Embed Views
3

Actions

Likes
0
Downloads
48
Comments
0

2 Embeds 3

http://www.slideshare.net 2
http://www.slashdocs.com 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Scrum And Sepg Scrum And Sepg Presentation Transcript

    • SCRUM and Software Engineering Process Group (SEPG) Mohan Bang [email_address]
    • Scrum Stands for SCRUM is not an acronym. Its proper spelling is Scrum (not all caps). It’s a rugby term used when members of the rugby teams form a circle to get the ball back into play. Think of Scrum as a way to get software delivery teams unstuck and moving again.
    • Scrum Scrum divides a project into sprints (aka iterations) of 30 days. Before you begin a sprint you define the functionality required for that sprint and leave the team to deliver it. But every day the team holds a short (10 – 15 minute) meeting, called a scrum where the team runs through what it will achieve in the next day. Some of the questions asked in the scrum meetings are: What did you do since the last scrum meetings? Do you have any obstacles? What will you do before next meeting? This is very similar to stand-up meetings in XP and iterative development process in RUP (Rational Unified Process). RUP has 4 phases in the following order Inception, Elaboration, Construction, and Transition. Agile (i.e. lightweight) software development process is gaining popularity and momentum across organizations. Several methodologies like XP, RUP, Scrum, FDD, TDD etc fit under this agile development methodology banner. All these methodologies share many characteristics like iterative and incremental development, stand-up meetings to improve communication, automatic build, testing and continuous integration etc.
    • Software Engineering Process Group (SEPG)
      • Software Engineering Process Group (SEPG)
      • Audit Process
      • Causal Analysis
      • Closure Analysis
      • Compliance Issues
      • Effort Distribution
      • Group review summary form
      • Introduction group reviews
      • Major Tasks
      • Performance Indicators
      • Process Database
      • Project Management Plan
      • As Quality Advisors
      • Process Infrastructure
      • Policies
      • Processes
      • Checklists, guidelines, templates, forms, standard tools, process database, process capability baseline
      • SEPG and Software Process Improvement Planning
      • Many factors are essential if process improvement initiatives are to succeed in an organization.
      • One success factor, which is also a key practice of the Organization Process Focus KPA (Key Process Area) of CMM (Capability Maturity Model) level 3, is the formation of a core group that takes responsibility for coordinating the process activities in the organization. This core group is commonly called the SEPG.
      • In IT companies, these SEPG will consist of quality professionals whose sole duty is monitoring and improving the processes for improving the Q&P in the organization. It includes approximately 1.5% of the company’s employees.
      • Effort Distribution of SEPG
      • Miscellaneous (30%)
      • Process Management (22%)
      • Process Implementation (28%)
      • Training (12%)
      • Audit (8%)
      • The task of defining a process consists of the following activities:
      • Initiate process definition
        • Create a draft sketch of the process
        • Obtain authorization from senior management
      • Define process
            • Identify life-cycle stages
            • Identify activities to a sufficient level of granularity
            • Identify inputs and outputs
            • Identify entry and exit criteria
            • Identify measurements, participants, and references
            • Write overview
            • Establish cross-reference to ISO and CMM, if necessary
      • Define tailoring guidelines
      • Review with users and senior management
      • Generate process definition following organizations standards
      • The main participants in this stage are the SEPG members, the members of the task force, process users, and senior management.
      • Major activities in Process Implementation phase of the process management process are as follows:
      • Launch the process
      • Pilot the process
        • Plan for piloting
        • Identify pilot projects
        • Define data collection and analysis plan for the pilot
        • Provide orientation to pilot project teams
        • Monitor pilot
        • Collect data, feedback, issues, and other information
        • Perform post-pilot analysis
        • Close pilot
      • Update draft process definition, if needed
      • Baseline updated process definition, if needed
      • Release formally
      • Conduct training
      • Deploy the process organization-wide.
      • The project management process is fairly standard, having three main stages:
      • Project planning
      • Project execution
      • Project closure
      • The PROJECT PLANNING stage:
      • Become familiar with the project
      • Create a project plan and schedule
        • Define project objectives
        • Plan for human resources
        • Define project organization
        • Identify a suitable standard process for project execution
        • Tailor the standard process to meet project requirements
        • Identify the methods, tools, templates, and standards to be used
        • Identify risks and define plans to mitigate them
        • Estimate effort
        • Define project milestones
        • Create a schedule for the project
        • Define a quality plan
        • Define a measurement plan for the project
        • Define a training plan for the project
        • Define project-tracking procedures
        • Define assumptions made in project planning
      • Perform group review for the project plan and schedule
      • Obtain authorization from senior management
      • Define and review the CM plan
      • Provide orientation to the project team.
      • The participants in this phase are the Project coordinator and Technical Architect (are responsible for developing the project plan), the onsite client, an SEPG representative, and the project manager for the project.
      • The PROJECT EXECUTION stage:
      • Track project status
      • Review project status with senior management
      • Manage requirement change
      • Monitor compliance to defined project process
      • Conduct milestone reviews
      • The participants in this phase are the same as the participants in the previous stage, with the addition of the project team.
    • The PROJECT CLOSURE stage: A systematic wind-up of the project after customer acceptance.
    • Thank You