@ARPITA Chakraborty  - Interesting question on this one.  Here are the things I think a blueprint champion would do:

• Be familiar with the latest updates to blueprint
• Understand the basic blueprinting flow:
  1. Use blueprint to ideate a process
  2. Capture all data needed to perform each step (without worrying about data model)
  3. Preview the case and gain acceptance of the blueprinted design
  4. Define a data model for the data collected during ideation specifically identifying the data needed to be retrieved via service or local lookup
  5. Complete sizing efforts (as needed)
  6. Request the generation of and access to services needed by the application (prior to project start)
  7. Make the blueprint as high-fidelity as possible given the current capabilities of blueprint
  8. At project start Review the latest blueprint capabilities
  9. Start iteratively delivering case types
     1. Select the next case type/types to import
     2. Update the selected case types to take advantage of the latest capabilities which may reduce the level of post-import work
     3. Export blueprint
     4. Import blueprint into pega
     5. Perform Finishing work on blueprint
        1. BAs refine UI and potentially close out stories
        2. Tech team works on technical stories and UI related stories that can't be fully completed by BAs
     6. Work is promoted to staging 
  10. Repeat step 8 until we are ready to promote to prod
  11. Perform QA and other implementation tasks as appropriate
• Help people learn the most efficient ways of leveraging blueprint to accelerate delivery - understanding this is a moving target as the product evolves rapidly.