Abhi bhalla a 02
- 1. KNOWLEDGE MANAGEMENT Submitted by, Abhi Bhalla A-02
- 3. Process Improvement Practices Implemented by Wipro • Big Data Ready Enterprise (BDRE) Framework. • Integrated Process Automation Tool (iPaT) • Information Security Management System (ISMS) • Sig Sigma • Lean principles, exemplified by the Toyota Production System (TPS)
- 4. Big Data Ready Enterprise (BDRE) • The BDRE framework essentially helps enterprises save thousands of laborious and expensive man-hours in deploying the technology. • Ways in which the BDRE framework actually simplifies things for enterprises:- 1. To begin with, you don’t have to build the platform from the ground up, saving you hundreds of man days. 2. Also, this being an Open Source platform, it lets your team contribute as well. 3. In other words, your Big Data implementations would get significant acceleration and letting you leverage data effortlessly to deliver quantum business growth.
- 5. Integrated Process Automation Tool (iPaT) • Integrated Process Automation Tool (iPaT) is a Web-based project management tracking tool, developed and maintained in-house. • iPAT is a single window for the entire project life cycle from initiation to closure. The tool is a storehouse of process assets such as templates, checklists, and process models • It is integrated with the organization’s Human Resources database for team details, audit tool for non-compliance closure details, and Wipro’s knowledge management system for Project Data Bank (PDB) data.
- 6. Integrated Process Automation Tool • iPAT is used by every practitioner, from project team members to the quality group, including senior management • Team members use iPAT to update work plans • Testing teams use iPAT for managing testing activities; and • Project managers use it for monitoring project status and activity management. • iPAT provides an automatically generated metrics scorecard at the end of the project and provides for an online approval mechanism.
- 7. Information Security Management System (ISMS)
- 8. SIX SIGMA • Wipro was one of the first companies to implement six sigma. • While ISO 9001 and the SEI-CMM helped in the definition and institutionalization of processes, a methodology was still needed to enable higher levels of optimization, directly resulting in lower costs and increased customer satisfaction. • Six Sigma methodologies were identified not only to address these challenges but also to aid in sustaining the process improvement. • Six Sigma directly contributes to Maturity Level 5—continuous optimization of key process areas.
- 9. SIX SIGMA • Six Sigma achieves dramatic improvement in business performance through a precise understanding of customer requirements and the elimination of defects from existing processes, products, and services. • Wipro decided to raise the quality bar in all key process areas to Six Sigma level. • Six Sigma was adopted as a management philosophy to encompass every sphere of work—from a secretary’s desk to the Chairman’s office.
- 10. SIX SIGMA Wipro chose to implement Six Sigma because :- • Six Sigma focused on the customer and was based on data integrated well with Wipro’s other quality initiatives • Was measurable, unlike other quality systems • Was an effective approach for removing defects from products and services • Was project based and provided immediate milestones • Gave them a competitive edge
- 11. LEAN • Back in 2004 no one had tried to apply manufacturing principles to software services and IT work at the scale that Wipro was operating. Four steps to Lean tasks: 1. Specify the task. 2. Streamline communication 3. Simplify the process architecture. 4. Adopt hypothesis-driven problem solving.
- 13. LEAN-TPS In addition, there were three challenges specific to software services: 1. Task uncertainty- The challenge is: how does a supplier standardize processes when the processes change rapidly. 2. Process invisibility. Often, employees do much of the work using ‘the knowledge in their heads’. Lean, on the other hand, ‘tries to bring everything out in the open’. 3. Architectural ambiguity. When creating software, the engineers often won’t know if it works until they do it.
- 14. THANK YOU